yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74627
[Bug 1791277] [NEW] The local vlan tag of openvswitch port become 4095 when dynamic segment is released
Public bug reported:
env: OpenStack Ocata, ml2 hierarchical port binding with openvswitch as
bottom driver
When the bottom segment already bound to a l2 driver is dynamiclly released,
the associated neutron.ml2_port_binding_levels.segment_id will be set "NULL",
and cause the local vlan tag of openvswitch port become 4095 (aka "dead vlan")
after an openvswitch restart.
The foreign key constraint:
|------------------------------------+--------------------+-----------|
| foreign key | reference | on delete |
|------------------------------------+--------------------+-----------|
| ml2_port_binding_levels.segment_id | networksegments.id | set null |
|------------------------------------+--------------------+-----------|
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
env: OpenStack Ocata, ml2 hierarchical port binding with openvswitch as
bottom driver
- When the bottom segment already bound to a l2 driver is dynamiclly released,
- the associated neutron.ml2_port_binding_levels.segment_id will be set "NULL",
- and cause the local vlan tag of openvswitch port become 4095 (aka "dead vlan")
+ When the bottom segment already bound to a l2 driver is dynamiclly released,
+ the associated neutron.ml2_port_binding_levels.segment_id will be set "NULL",
+ and cause the local vlan tag of openvswitch port become 4095 (aka "dead vlan")
after an openvswitch restart.
The foreign key constraint:
- |--------------------------------------------+----------------------------+-----------|
- | foreign key | reference | on delete |
- |--------------------------------------------+----------------------------+-----------|
- | neutron.ml2_port_binding_levels.segment_id | neutron.networksegments.id | set null |
- |--------------------------------------------+----------------------------+-----------|
+ |------------------------------------+--------------------+-----------|
+ | foreign key | reference | on delete |
+ |------------------------------------+--------------------+-----------|
+ | ml2_port_binding_levels.segment_id | networksegments.id | set null |
+ |------------------------------------+--------------------+-----------|
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1791277
Title:
The local vlan tag of openvswitch port become 4095 when dynamic
segment is released
Status in neutron:
New
Bug description:
env: OpenStack Ocata, ml2 hierarchical port binding with openvswitch
as bottom driver
When the bottom segment already bound to a l2 driver is dynamiclly released,
the associated neutron.ml2_port_binding_levels.segment_id will be set "NULL",
and cause the local vlan tag of openvswitch port become 4095 (aka "dead vlan")
after an openvswitch restart.
The foreign key constraint:
|------------------------------------+--------------------+-----------|
| foreign key | reference | on delete |
|------------------------------------+--------------------+-----------|
| ml2_port_binding_levels.segment_id | networksegments.id | set null |
|------------------------------------+--------------------+-----------|
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1791277/+subscriptions