yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #75226
[Bug 1797368] [NEW] Trunk: different behavior of admin_state_up attribute between trunk and port
Public bug reported:
High level description:
The behavior of admin_state_up attribute is different between port and trunk which may impact user experience.
Environments: configure neutron to use openvswitch agent
Version: latest devstack
Steps to reproduce:
1. create network/subnet/port
2. update port to set admin_state_up = FALSE (which will set port status to “Down”, then disable the port to block send/receive packages, e.g. set port’s tap device state to down or move the port to DEAD_VLAN etc.)
3. verify the port cannot work
result: the port can not send/receive packages
4. create trunk
5. update trunk to set admin_state_up = FALSE (which will lock the trunk to prevent operations such as adding/removing subports)
6. check whether the trunk is still operational
Expected output: the trunk will stop to process VLAN packets arriving from VM instance
Actual output: the trunk is still operational (e.g. the trunk sub-port can still send/receive packages)
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1797368
Title:
Trunk: different behavior of admin_state_up attribute between trunk
and port
Status in neutron:
New
Bug description:
High level description:
The behavior of admin_state_up attribute is different between port and trunk which may impact user experience.
Environments: configure neutron to use openvswitch agent
Version: latest devstack
Steps to reproduce:
1. create network/subnet/port
2. update port to set admin_state_up = FALSE (which will set port status to “Down”, then disable the port to block send/receive packages, e.g. set port’s tap device state to down or move the port to DEAD_VLAN etc.)
3. verify the port cannot work
result: the port can not send/receive packages
4. create trunk
5. update trunk to set admin_state_up = FALSE (which will lock the trunk to prevent operations such as adding/removing subports)
6. check whether the trunk is still operational
Expected output: the trunk will stop to process VLAN packets arriving from VM instance
Actual output: the trunk is still operational (e.g. the trunk sub-port can still send/receive packages)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1797368/+subscriptions
Follow ups