Datasource driver load error not properly handled

Bug #1435524 reported by Tim Hinrichs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
congress
Fix Released
Medium
Sayaji Patil

Bug Description

In congress/managers/datasource.py, in the add_datasource method, we call

                cage.createservice(name=datasource['name'],
                                   moduleName=driver_info['module'],
                                   args=datasource['config'],
                                   module_driver=True)

without catching the possible DataServiceError that this method throws. If it throws a DataServiceError, we should call

                    engine.delete_policy(datasource['name'])

and then reraise the error.

Sayaji Patil (sayaji15)
Changed in congress:
assignee: nobody → Sayaji Patil (sayaji15)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to congress (master)

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

Changed in congress:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on congress (master)

Change abandoned by Tim Hinrichs (<email address hidden>) on branch: master
Review: https://review.openstack.org/169581
Reason: This was a good change, but it didn't get merged b/c of a merge conflict for long enough that someone else fixed the same bug in a separate changeset.

Tim Hinrichs (thinrichs)
Changed in congress:
status: In Progress → 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.