Comment 6 for bug 2049574

Revision history for this message
Aravindh (highlow7) wrote :

@SvenKieske I updated OS-brick to the master branch on the nova container and the issue still persists.

VM still stuck in hard-reboot phase.

Wierd behavior I noticed now is

- When the VM (say rocky) reboots and multipath is in failed state, the volume becomes available in openstack
- Used that volume to create a new instance (say rocky-new). Now both the VM are shown up.
- Volume page tells me that this volume is now attached to rocky-new. But taking console, bring straight to emergency mode on rocky-new.
- Rocky VM some how is now active and works fine?