Reviewed: https://review.opendev.org/c/openstack/nova/+/904817 Committed: https://opendev.org/openstack/nova/commit/b5173b419219437b50f49c88bce9727ed0ed1ee8 Submitter: "Zuul (22348)" Branch: master
commit b5173b419219437b50f49c88bce9727ed0ed1ee8 Author: Amit Uniyal <[email protected]> Date: Fri Jan 5 08:41:29 2024 +0000 Fixes: bfv vm reboot ends up in an error state. we only need to verify if bdm has attachment id and it should be present in both nova and cinde DB. For tests coverage, added tests for bfv server to test different bdm source type. Closes-Bug: 2048154 Closes-Bug: 2048184 Change-Id: Icffcbad27d99a800e3f285565c0b823f697e388c ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/2048184 Title: VM, booted from volume end up on Error state on reboot Status in OpenStack Compute (nova): Fix Released Bug description: Description =========== A VM created as booted from volume, went to error state on reboot. reason Volume attachment is getting deleted at Cinder side. https://paste.opendev.org/show/bgMKY9lwrIatIJ6Acl0H/ Steps to reproduce ================== 1- Create a VM. $ openstack server create --flavor 1 --network private --image cirros --boot-from-volume 1 vm1 wait for VM to become Active 2 - Reboot VM $ openstack server reboot vm1 Expected result =============== Server should not go to error state Actual result ============= Server went to error state Environment =========== devstack setup Logs & Configs ============== error from compute log: https://paste.opendev.org/show/b365smdQWNA7A0MwK3s5/ full compute logs: attached To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2048184/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
