Zookeeper persistence backend not creating new atoms
Bug #1395812 reported by
Joshua Harlow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| taskflow |
Fix Released
|
High
|
Joshua Harlow | ||
Bug Description
It appears the zookeeper persistence backend is blowing up with not found atoms when it should instead be creating them; this makes the zookeeper persistence backend currently unusable due to this issue.
| Changed in taskflow: | |
| importance: | Undecided → High |
| assignee: | nobody → Joshua Harlow (harlowja) |
| Changed in taskflow: | |
| status: | New → In Progress |
| Changed in taskflow: | |
| milestone: | none → next-kilo |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to taskflow (master) | #1 |
| Changed in taskflow: | |
| status: | In Progress → Fix Committed |
| Changed in taskflow: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2832d6e677413d0
Author: Joshua Harlow <email address hidden>
Date: Fri Nov 21 13:07:47 2014 -0800
Ensure that the zookeeper backend creates missing atoms
When 'create_missing' is true the atom should be created
instead of raising an exception; this is used when a flow
detail is updated with a new detail and then saved.
This also adds test cases that verify this happens so that
we verify this on an ongoing basis.
Fixes bug 1395812
Change-Id: I4851a08ff1ab41