network interfaces on the vnf instance does not come up in the same sequence as specified in the vnfd template
Bug #1504687 reported by
Sripriya
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
Fix Released
|
High
|
Sripriya | ||
Bug Description
management, net0 and net1 network interfaces come up in a random order on the vnf instance. as a user, i need the network interfaces to come up in the same sequence as mentioned in the template
| Changed in tacker: | |
| assignee: | nobody → Sripriya (sseetha) |
| Changed in tacker: | |
| status: | New → In Progress |
| Changed in tacker: | |
| importance: | Undecided → High |
| tags: | added: liberty-critical |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to tacker (master) | #1 |
| Changed in tacker: | |
| status: | In Progress → Fix Committed |
| Changed in tacker: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit dc5024e232f4cfb
Author: Sripriya <email address hidden>
Date: Mon Oct 12 14:01:15 2015 -0700
Preserve network interfaces order of vnfd template
The Python dictionary behavior of vnfd body does not guarantee the
network interfaces to be fetched in same order as specified in template.
This fix uses the third party python package tosca-parser to preserve
the order. This will ensure the interfaces come up in the same sequence
as specified in template.
Closes-Bug: #1504687
Change-Id: Ieddd2ba1632886