Public bug reported: 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/manager.py starting at line 1923. The ImageNotFound exception should be included in the list at line 1960 so the BuildAbortException is thrown, which will be caught and handled correctly further up the stack. ** Affects: nova Importance: Undecided Assignee: Paul Murray (pmurray) Status: New ** Changed in: nova Assignee: (unassigned) => Paul Murray (pmurray) -- 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/1632042 Title: ImageNotFound is not correctly handled by compute manager Status in OpenStack Compute (nova): New 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/manager.py starting at line 1923. The ImageNotFound exception should be included in the list at line 1960 so the BuildAbortException is thrown, which will be caught and handled correctly further up the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1632042/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp