Logging exception.message does not log properly when the actual exception is initialized with keyword arguments

Bug #1520291 reported by Magesh GV
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy
Confirmed
Medium
Ivar Lazzaro

Bug Description

There are a few places where we are logging exception.message which does not log correctly when the actual exception class message was initialized with keyword arguments.

21541: DEBUG gbpservice.neutron.services.servicechain.plugins.ncp.plumber_base [-] Policy Target %(policy_target_id)s could not be found _delete_service_targets /usr/lib/python2.7/site-packages/gbpservice/neutron/services/servicechain/plugins/ncp/plumber_base.py:120

6569: WARNING gbpservice.neutron.services.servicechain.plugins.ncp.node_driver_manager [-] The Service flavor %(service_flavor)s for service type %(service_type)s is not allowed for %(managed)s project

Changed in group-based-policy:
importance: Undecided → Medium
assignee: nobody → Ivar Lazzaro (mmaleckk)
milestone: none → next
status: New → Confirmed
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.