Port binding fails for DVS when single_tenant_mode = False

Bug #1590830 reported by Thomas Bachman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy
Confirmed
Medium
Thomas Bachman

Bug Description

The dvs_port_group_name created by the mechanism driver is incorrect when single_tenant_mode = False. The name constructed is missing the APIC scoping. For example, given an apic_system_id = openstack2, and a tenant network named net04 created in the admin OpenStack project, the port group constructed is:

admin|openstack_app|net04

But it should be:

_openstack2_admin|openstack_app|net04

This causes port binding to fail for DVS ports, due to the port group not existing (looks for the admin|openstack_app|net04 port group, but it's not there -- though the _openstack2_admin|openstack_app|net04 port group is).

Changed in group-based-policy:
milestone: none → next
assignee: nobody → Thomas Bachman (bachman)
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.