ImageNotFound is not correctly handled by compute manager
Bug #1632042 reported by
Paul Murray
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned | ||
Newton |
New
|
Undecided
|
Unassigned |
Bug Description
When building an instance, if the glance client throws an ImageNotFound exception the compute manager will reschedule the instance without cleaning up any networks that have been built out, leaking any ports that have been created.
The correct behaviour should include cleaning up allocated networks and abandoning the instance creation, leaving it in error.
The relevant exception handling is in nova/compute/
Changed in nova: | |
assignee: | nobody → Paul Murray (pmurray) |
Changed in nova: | |
status: | In Progress → Confirmed |
assignee: | nobody → Sivasathurappan Radhakrishnan (siva-radhakrishnan) |
Changed in nova: | |
assignee: | Sivasathurappan Radhakrishnan (siva-radhakrishnan) → nobody |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/384649
Review: https:/