Job consumption example in Job documentation has incorrect usage of persistence backend
Bug #1408434 reported by
Min Pae
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
taskflow |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Job consumption example in Job documentation calls destroy_logbook on the persistence backend instance when the method lives in the connection, not the backend.
Changed in taskflow: | |
milestone: | none → 0.7.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/145574 /git.openstack. org/cgit/ openstack/ taskflow/ commit/ ?id=a18a939aae1 dff42a4741a1852 829abe5280aa80
Committed: https:/
Submitter: Jenkins
Branch: master
commit a18a939aae1dff4 2a4741a1852829a be5280aa80
Author: Min Pae <email address hidden>
Date: Wed Jan 7 12:26:19 2015 -0800
Fix for job consumption example using wrong object
Change job consumption example in Job documentation to use .get_connection ().destroy_ logbook( ) instead of .destroy_ logbook( )
persistence
persistence
Change-Id: Ia6d0f2be4dd7cd 161ef7b6d8afc32 aab532fd69b
Closes-Bug: 1408434