Designate record deletion is broken
Bug #1463058 reported by
Chris St. Pierre
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Rally |
Fix Released
|
Medium
|
Chris St. Pierre | ||
Bug Description
Deleting Designate records is partially broken. The _delete_record() utility function accepts a flag, atomic_action; if atomic_action is True, then a new record is created, and then it is deleted. (Record creation should fail in this case, though, since presumably it already exists if the task is trying to delete it.)
Currently _delete_record() is not called anywhere with atomic_action=True, which is why this has been hidden thus far.
| Changed in rally: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Chris St. Pierre (stpierre) |
| milestone: | none → 0.1.0 |
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: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 45fa4673f3a8046
Author: Chris St. Pierre <email address hidden>
Date: Mon Jun 8 09:40:06 2015 -0500
Fix Designate record deletion utility function
Change-Id: Ifa9fa2e7115612
Closes-Bug: 1463058