Skip to content

docs(instance-recovery): document delayed evacuation for Cinder boot volumes #218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gboutry merged 1 commit into from
Jun 24, 2026
Merged

docs(instance-recovery): document delayed evacuation for Cinder boot volumes #218

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions how-to/features/instance-recovery.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,6 +483,22 @@ This section contains information that can be useful when working with Masakari.

openstack segment host update --reserved=<boolean> SEGMENT HOSTNAME

* VMs booting from a Cinder volume with ``multiattach=False`` might not be evacuated within the
Masakari evacuation window. Nova can trigger evacuation while waiting for Cinder to detach the
volume from the source host. In this case, the evacuation remains pending until the original
attachment is released or the source host becomes available again.

As a workaround, fence the failed source host or otherwise confirm that it is powered off and
that the original attachment is no longer active before resetting the Cinder volume state:

.. code-block:: bash

openstack volume set --state available <volume id>

Resetting the volume state earlier can allow the same boot volume to be attached on another host
while it is still in use on the source host, which can corrupt the guest filesystem.


Limitations
-----------

Expand Down
Loading