Boot from volumes that fail in initialize_connection are not rescheduled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Version: OpenStack Liberty
Boot from volumes that fail in volume initialize_
The instance is not rescheduled because the initialize_
nova.compute.
nova.compute.
nova.virt.
nova.virt.
When this fails an exception is thrown which lands in this block:
https:/
and throws an InvalidBDM exception which is caught by this block:
https:/
this in turn throws a BuildAbortException which causes the instance to not be rescheduled by landing the flow in this block:
https:/
To fix this we likely need a different exception thrown from nova.virt.
Changed in nova: | |
assignee: | nobody → Samuel Matzek (smatzek) |
tags: | added: spawn volumes |
tags: |
added: compute removed: spawn |
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: liberty-backport-potential |
no longer affects: | mitaka (Ubuntu) |
Changed in nova: | |
assignee: | Samuel Matzek (smatzek) → nobody |
Fix proposed to branch: master /review. openstack. org/246505
Review: https:/