Public bug reported: The _device_to_port_id method in ML2 accepts either an interface name, a port UUID, or a MAC address and returns the corresponding port ID.
The part that takes an interface name currently only works if the interface prefix is 'tap'. This is broken in the cases where security group filtering is used ('qvo' prefix) and snat interfaces ('sg-'). This is okay in the cases where the external id is loaded directly into the database, but it doesn't work for vswitches that don't have OVSDB or when scripts have re-added the interface to the vswitch without the external ID. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1443710 Title: _device_to_port_id broken for many devices Status in OpenStack Neutron (virtual network service): New Bug description: The _device_to_port_id method in ML2 accepts either an interface name, a port UUID, or a MAC address and returns the corresponding port ID. The part that takes an interface name currently only works if the interface prefix is 'tap'. This is broken in the cases where security group filtering is used ('qvo' prefix) and snat interfaces ('sg-'). This is okay in the cases where the external id is loaded directly into the database, but it doesn't work for vswitches that don't have OVSDB or when scripts have re-added the interface to the vswitch without the external ID. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1443710/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp