heat stack-update failed when removing a VLAN

Bug #1768493 reported by Sowmya Divvi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Confirmed
Medium
Unassigned

Bug Description

I have tried to remove a VLAN in yaml template by updating stack, but it's failed with the error message
"Resource update failed:BadRequest : resources.subport:invalid input for operation vlan id is used already on trunkport."

success scenario:
I have launched stack with specifying following vlans:

vlan_ids: ['116', '118', '119']

and updated stack with vlan_ids: ['116', '118']

stack create and update are successful.

Fail scenario:

I have launched stack with specifying following vlans:

vlan_ids: ['116', '118', '119']

and updated stack with vlan_ids: ['116', '119']

stack update is failed.

While updating stack, it's unable to delete the middle vlan.

(i.e)In above case i am unable to delete vlan '118' but with the last vlan(119) in the right, we didn't have any problems while updating the stack.

Revision history for this message
Thomas Herve (therve) wrote :

Please attach the templates used, thanks

Changed in heat:
status: New → Incomplete
importance: Undecided → Medium
milestone: none → next
milestone: next → ongoing
Changed in heat:
status: Incomplete → Confirmed
Revision history for this message
Sowmya Divvi (sowmya) wrote :
Revision history for this message
Sowmya Divvi (sowmya) wrote :
Revision history for this message
Sowmya Divvi (sowmya) wrote :
Revision history for this message
Sowmya Divvi (sowmya) wrote :
Revision history for this message
Sowmya Divvi (sowmya) wrote :

I have used hot.yaml as main template and vsg_env.yaml as environment file and vsg_pmp as nested template to launch stack and vsg_update.yaml to update the stack

Changed in heat:
assignee: nobody → Kumari Paluru (kumariopenstack)
Changed in heat:
assignee: Kumari Paluru (kumariopenstack) → nobody
Changed in heat:
assignee: nobody → Kumari Paluru (kumariopenstack)
Changed in heat:
assignee: Kumari Paluru (kumariopenstack) → nobody
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.