Keystone does not clean up services
Bug #1474322 reported by
Chris St. Pierre
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Rally |
Fix Released
|
High
|
Chris St. Pierre | ||
Bug Description
Keystone resources are only cleaned up if their name starts with "rally_keystone_", but services can be created with arbitrary names that do not include that prefix. This prevents them from being cleaned up afterward. The samples shipped with Rally do not start with the correct prefix.
| Changed in rally: | |
| status: | New → In Progress |
| assignee: | nobody → Chris St. Pierre (stpierre) |
| importance: | Undecided → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to rally (master) | #1 |
| Changed in rally: | |
| status: | In Progress → Fix Committed |
| Changed in rally: | |
| milestone: | none → 0.1.0 |
| 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 9f2e4abc366b315
Author: Chris St. Pierre <email address hidden>
Date: Wed Jul 8 16:10:54 2015 -0500
Keystone: do not allow specifying service names
This fixes service cleanup. Keystone resources are only cleaned up if
they have the correct magic prefix, but services were not reliably
created with that prefix.
This also adds some logging that made it easier to discover this
issue, and fixes a few minor typos.
Closes-Bug: #1474322
Change-Id: Ic58271bbc9a84f