CVM should set new VLAN ID after vMotion
Bug #1783979 reported by
Adrian Szczepański
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R5.0 |
Fix Committed
|
High
|
Unassigned | |||
| Trunk |
Fix Committed
|
High
|
Unassigned | |||
| OpenContrail |
New
|
Undecided
|
Unassigned | |||
Bug Description
There is a possibility that after vMotion, CVM retains old VLAN ID of an interface which may collide with existing interfaces on the new host.
We should check if the current VLAN ID of the interface is available on the host and if not, assign new VLAN ID.
| Changed in opencontrail: | |
| assignee: | nobody → Adrian Szczepański (adrian.szczepanski) |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote [Review update] R5.0 | #1 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote [Review update] master | #3 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #5 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote | #6 |
To post a comment you must log in.
Review in progress for https:/
Submitter: Adrian Szczepanski (<email address hidden>)