Provide additional logging from execute()

Bug #1342857 reported by Amrith Kumar on 2014-07-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.concurrency
Undecided
Amrith Kumar

Bug Description

In bug 1340124 [https://bugs.launchpad.net/trove/+bug/1340124 ] there is a request to provide some additional logging about the error that occurred when an error occurs in execute().

The change for this https://review.openstack.org/#/c/106008/ is making a change to execute_with_timeout() in the trove code but this request is to make a similar change in the oslo code such that all modules can benefit from this, as it will generate a single standardized message for all clients who request this additional logging.

Amrith Kumar (amrith) on 2014-07-16
Changed in oslo:
assignee: nobody → Amrith (amrith)

Fix proposed to branch: master
Review: https://review.openstack.org/108216

Changed in oslo:
status: New → In Progress

Change abandoned by amrith (<email address hidden>) on branch: master
Review: https://review.openstack.org/108216
Reason: I am abandoning https://review.openstack.org/#/c/108216/ and https://review.openstack.org/#/c/108215/ and will create a new commit with proper dependencies.

Fix proposed to branch: master
Review: https://review.openstack.org/109469

Change abandoned by amrith (<email address hidden>) on branch: master
Review: https://review.openstack.org/109469
Reason: Resubmitted change to oslo.concurrency.

https://review.openstack.org/#/c/114659/

affects: oslo-incubator → oslo.concurrency
Amrith Kumar (amrith) on 2014-10-16
Changed in oslo.concurrency:
status: In Progress → Fix Committed
Changed in oslo.concurrency:
milestone: none → 0.1.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers