Zookeeper persistence backend not creating new atoms

Bug #1395812 reported by Joshua Harlow
6
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.

Joshua Harlow (harlowja)
Changed in taskflow:
importance: Undecided → High
assignee: nobody → Joshua Harlow (harlowja)
Changed in taskflow:
status: New → In Progress
Joshua Harlow (harlowja)
Changed in taskflow:
milestone: none → next-kilo
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to taskflow (master)

Reviewed: https://review.openstack.org/136491
Committed: https://git.openstack.org/cgit/openstack/taskflow/commit/?id=2832d6e677413d08bd1645bb8bd8067b3ab665d6
Submitter: Jenkins
Branch: master

commit 2832d6e677413d08bd1645bb8bd8067b3ab665d6
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: I4851a08ff1ab4101dbec4a6656177908095c3c52

Changed in taskflow:
status: In Progress → Fix Committed
Joshua Harlow (harlowja)
Changed in taskflow:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.