Cannot create router interface on network with non-Neutron port

Bug #1533629 reported by Brandon Berg on 2016-01-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
midonet
Fix Committed
Medium
Brandon Berg
networking-midonet
Undecided
YAMAMOTO Takashi

Bug Description

When attempting to create a RouterInterface on a network which has a non-Neutron (Midonet-only) port, RouterInterfaceTranslator.createMetaDataServiceRoute attempts to get the NeutronPorts for all of the Midonet network's port IDs. The Midonet-only ports will not have a corresponding NeutronPort, and this will fail. The query of all NeutronPorts is an attempt to get the DHCP port to find its address to use to create the metadata service route. Instead of doing this, we should just use the Dhcp's server_address property, which is a) much more efficient and b) doesn't cause the whole operation to fail.

YAMAMOTO Takashi (yamamoto) wrote :

not a plugin issue.
i added midonet to the list of affected projects.

Changed in networking-midonet:
assignee: nobody → YAMAMOTO Takashi (yamamoto)
status: New → Invalid
Changed in midonet:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 5.1
assignee: nobody → Brandon Berg (bberg-s)
JF Joly (jfj) wrote :
Changed in midonet:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers