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!
Public Cloud - Failedattachvolume on another node
Related questions
- IPv6 subnet/extra IPv6 IPs on cloud instances/VPS
8358
31.01.2018 07:31
- Problem with Windows Server 2019 activation
7661
30.12.2020 04:04
- Is the Plesk License included?
7227
02.01.2018 11:56
- Ubuntu 20.04 image in OVH has been marked as DEPECRATED
6504
04.12.2020 23:28
- Automatic Block storage backup - how?
5674
06.05.2020 17:31
- Private Network shared between two or more Public Cloud projects
5551
11.03.2021 13:19
- Can i use my own public cloud vm with floating ip as internet gatewaway for my private network?
5349
26.01.2026 08:13
- Setup clickhouse with s3 high performance storage class (express onezone)
5107
16.10.2025 13:28
- Error has occurred creating your Public Cloud project
4816
08.10.2021 08:52
- CORS in Object Storage
4798
03.11.2020 06:02