Tackerclient failed to handle yaml load error.

Bug #1780214 reported by dharmendra
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Committed

Bug Description

While onboarding a vnfd with infected vnfd file, yaml.load raised exception. But tacker client failed to handle it, and raised traces.

ubuntu@openstack-nti-4:~$ openstack vnf descriptor create --vnfd-file ~/test_vnfd.yaml vnfd1
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 861, in emit
    msg = self.format(record)
  File "/usr/lib/python2.7/logging/__init__.py", line 734, in format
    return fmt.format(record)
  File "/usr/lib/python2.7/logging/__init__.py", line 465, in format
    record.message = record.getMessage()
  File "/usr/lib/python2.7/logging/__init__.py", line 325, in getMessage
    msg = str(self.msg)
TypeError: __str__ returned non-string (type ScannerError)
Logged from file app.py, line 407

Changed in tacker:
assignee: nobody → dharmendra (dharmendra-kushwaha)
importance: Undecided → Medium
Revision history for this message
dharmendra (dharmendra-kushwaha) wrote :
Changed in tacker:
status: New → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tackerclient 0.13.0

This issue was fixed in the openstack/python-tackerclient 0.13.0 release.

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.