Failedattachvolume on another node
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Question

Failedattachvolume on another node

by
NilsM
Created on 2023-06-26 07:23:27 (edited on 2024-09-04 14:23:10) in Public Cloud

I ran a new deployment normally.
The deployment uses an existing volume.
I tried several times and each time I got the error "Failedattachvolume". There was a lot of text, including that the volume is already in-use.

Unfortunately I did not take a screenshot.

I have a nodepool of 2 nodes. Currently all pods are running on one node. But the deployment was apparently executed on the other node. Can this be the reason?
In the overview on the OVH Cloud interface, all volumes seem to be connected to the first node only.

I therefore assumed that the volume cannot be connected because it is only available on the first node. My solution was therefore to configure the node during deployment using `nodeName: mycluster-node-d2aa28`. Then everything worked without problems.

But for the future I would be interested now, what was the reason for this and how I can avoid the problem also with multiple nodes.

Thanks!