Hey, Most of our instances are having local disk. And some of them have attached volumes. Evacuation does not seem possible in that situation, am I wrong? Moreover, evacuation seems an administrator option, not beeing able to be triggered from an user action. My use case is the following: I have a region with multiple AZ, cross_az attachment is allowed for my volumes. There is no issue to attach / detach until the the compute is down. The compute could be down when an AZ is down. In that situation, a use may want to force detach the volume and re-attach it to another instances in another AZ. Regards, Arnaud On 21.03.25 - 17:00, Amit Uniyal wrote:
Hello, I think we usually have an evacuation api for this. Is there any reason you do not want to evacuate instance, then the volume will stay attached and usuable ?
Regards
On Fri, Mar 21, 2025 at 4:34 PM Arnaud Morin <arnaud.morin@gmail.com> wrote:
I can partially answer myself. This is a feature, which prevent inconsistencies from nova/cinder.
https://review.opendev.org/c/openstack/nova/+/768352 https://bugs.launchpad.net/nova/+bug/1909120
Now, I am wondering if multiattach could be a partial solution?
Cheers, Arnaud
On 20.03.25 - 13:49, Arnaud Morin wrote:
Hey team,
Is there any way to force detach a volume when the nova compute service is down? Like when the hypervisor is off, we want to detach the volume and attach it to another instance.
Maybe I'm missing the way to do it, but detach action on nova side seems a synchronous task that I can't force without admin creds.
Thanks for any help,
Regards, Arnaud