failed customization by custom_image leaves VM running
Bug #1502832 reported by
Pavel Boldin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Rally |
Fix Released
|
Medium
|
Pavel Boldin | ||
Bug Description
Whenever customization script run on a remote host by `custom_image` fails the corresponding VM is left running.
This piles up networks, routers and VMs.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to rally (master) | #1 |
| Changed in rally: | |
| status: | New → Fix Committed |
| Changed in rally: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Pavel Boldin (pboldin) |
| tags: | added: plugin task |
| Changed in rally: | |
| milestone: | none → 0.1.1 |
| Changed in rally: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5d5eeea8ed43cf1
Author: Pavel Boldin <email address hidden>
Date: Sun Sep 27 05:42:32 2015 +0300
workload: fix custom_image cleanup
A VM ran by `custom_image` context is left running in case the script
failed. Fix this by moving cleanup to a try/finally block letting
the exception propagate upwards so no scenario is run when the context
have failed.
Change-Id: I90d783eeb50b1f
Closes-Bug: #1502832