yahoo-eng-team team mailing list archive

["Le, Huifeng" <1794424@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

High level description:
For agent such as linux bridge which allows creating trunk on bound port, it is not allowed to delete the trunk if not unbound the port (parent-port) first. It will break the use scenario which expect to keep the port's (trunk's parent port) communication while delete the trunk.
The issue can be reproduced on the latest devstack.

Environments:configure to use linux bridge agent
Version: latest devstack

Steps to reproduce:
1. create network/subnet/trunk parent port/trunk sub port
openstack network create net0
openstack subnet create --network net0 --subnet-range 10.0.4.0/24 subnet0
openstack port create --network net0 trunk1_port
parent_trunk1_mac="$( openstack port show trunk1_port | awk '/ mac_address / { print $4 }' )"
openstack port create --network net1 --mac-address "$parent_trunk1_mac" trunk1_subport1
result: success

2. create VM (bound trunk parent port first)
openstack server create --flavor ds512M --image vlan-capable-image --nic port-id="$trunk1_port_id" --wait vm_trunk1
result: success

3. create trunk: openstack network trunk create --parent-port trunk1_port --subport port=trunk1_subport1,segmentation-type=vlan,segmentation-id=101 trunk1
result: success

4. delete trunk:
openstack network trunk delete trunk1
Expected output: success
Actual output: fail with message "Trunk trunk1 is currently in use"

** Affects: neutron
     Importance: Undecided
     Assignee: Le, Huifeng (hle2)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Le, Huifeng (hle2)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1794424

Title:
  trunk: can not delete bound trunk for agent which allow create trunk
  on bound port

Status in neutron:
  New

Bug description:
  High level description:
  For agent such as linux bridge which allows creating trunk on bound port, it is not allowed to delete the trunk if not unbound the port (parent-port) first. It will break the use scenario which expect to keep the port's (trunk's parent port) communication while delete the trunk.
  The issue can be reproduced on the latest devstack.

  Environments:configure to use linux bridge agent
  Version: latest devstack

  Steps to reproduce:
  1. create network/subnet/trunk parent port/trunk sub port
  openstack network create net0
  openstack subnet create --network net0 --subnet-range 10.0.4.0/24 subnet0
  openstack port create --network net0 trunk1_port
  parent_trunk1_mac="$( openstack port show trunk1_port | awk '/ mac_address / { print $4 }' )"
  openstack port create --network net1 --mac-address "$parent_trunk1_mac" trunk1_subport1
  result: success

  2. create VM (bound trunk parent port first)
  openstack server create --flavor ds512M --image vlan-capable-image --nic port-id="$trunk1_port_id" --wait vm_trunk1
  result: success

  3. create trunk: openstack network trunk create --parent-port trunk1_port --subport port=trunk1_subport1,segmentation-type=vlan,segmentation-id=101 trunk1
  result: success

  4. delete trunk:
  openstack network trunk delete trunk1
  Expected output: success
  Actual output: fail with message "Trunk trunk1 is currently in use"

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1794424/+subscriptions