tacker

YAML well formedness check missing as part of vnf-update operation

Bug #1500293 reported by vishwanath jayaraman on 2015-09-28

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tacker	Won't Fix	Low	Unassigned

The file https://github.com/stackforge/tacker/blob/master/tacker/vm/drivers/heat/heat.py#L344 is not checking if the end user supplied config update contents is YAML well formed or not. The code also needs to indicate to the end user that vnf-update cannot be applied if the config contents are not YAML well formed.

See original description

Tags:

vishwanath jayaraman (vishwanathj) on 2015-09-28

Revision history for this message

Sridhar Ramaswamy (srics-r) wrote on 2015-09-30:

Perhaps we can fix this bug along with https://bugs.launchpad.net/tacker/+bug/1483953 by uniformly adding an exception handler for all yaml load operations.

Changed in tacker:
importance:	Undecided → Low

Anshu Kumar (anshu-choubey) on 2016-06-20

Changed in tacker:
assignee:	nobody → Anshu Kumar (anshu-choubey)

Anshu Kumar (anshu-choubey) on 2016-06-20

Changed in tacker:
assignee:	Anshu Kumar (anshu-choubey) → nobody

Revision history for this message

Anshu Kumar (anshu-choubey) wrote on 2016-06-20:

Unassigned because the loosely associated bug is assigned by Neeldhwaj Pathak (neel)

Revision history for this message

dharmendra (dharmendra-kushwaha) wrote on 2017-11-28:

As tosca already in place. Closing this.

Changed in tacker:
status:	New → Won't Fix

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.