https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NEUTRON-43 neutron <p>A neutron port created for floating IP does not contain tenant information.</p> <p>This is NeutronPort.toString() when method neutronPortCreated(NeutronPort port) is invoked on implementation of INeutronPortAware:<br/> NeutronPort [portUUID=0e004b2d-84ac-4725-b8f5-dfce251d31d8, networkUUID=a61a5705-a21d-4a04-932a-10f8f36516e2, name=, adminStateUp=true, status=null, macAddress=FA:16:3E:CB:30:F1, fixedIPs=[Neutron_IPs</p> {ipAddress='192.168.111.51', subnetUUID='1453aeec-203c-40c2-8a94-48331c6c0541'} <p>], deviceID=2cb9cff7-4ec0-4d8b-86b8-3bf0b8328fce, deviceOwner=network:floatingip, tenantID=, floatingIPMap={}, securityGroups=[], bindinghostID=, bindingvnicType=normal, bindingvnicType=normal]</p> <p>The same issue with NeutronPort passing to the method canCreatePort(NeutronPort port)</p> <p>Operating System: All<br/> Platform: All</p> NEUTRON-43

Missing tenantID in NeutronPort for floatingIp port

Bug Resolved Done Unassigned Martin Sunal Mon, 25 May 2015 20:31:19 +0000 Thu, 19 Oct 2017 21:29:07 +0000 Mon, 22 Jun 2015 07:57:33 +0000 Multiple External 0 4 <p><a href="https://git.opendaylight.org/gerrit/21794" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/21794</a> shows that this isn't a bug with NN but an issue in openstack/devstack</p> <p>(output from Jenkins build:</p> <p>2015-06-03 16:52:32,054 | INFO | qtp736031520-81 | NeutronNetworkDummyProvider | 258 - org.opendaylight.neutron.dummyprovider - 0.5.0.SNAPSHOT | NeutronNetwork [networkUUID=4e8e5957-649f-477b-9e5b-f1f75b21c03c, networkName=net1, adminStateUp=true, shared=false, tenantID=9bacb3c5d39d41a79512987f338cf177, routerExternal=false, providerNetworkType=flat, providerPhysicalNetwork=null, providerSegmentationID=null, status=ACTIVE, subnets=[], myPorts=[], segments = [NeutronNetwork_Segment [ , providerNetworkType=vlan, providerPhysicalNetwork=8bab8453-1bc9-45af-8c70-f83aa9b50453, providerSegmentationID=2], NeutronNetwork_Segment [ , providerNetworkType=stt, providerPhysicalNetwork=8bab8453-1bc9-45af-8c70-f83aa9b50453, providerSegmentationID=null]]]<br/> 2015-06-03 16:52:32,179 | INFO | qtp736031520-81 | NeutronSubnetDummyProvider | 258 - org.opendaylight.neutron.dummyprovider - 0.5.0.SNAPSHOT | NeutronSubnet [subnetUUID=3b80198d-4f7b-4f77-9ef5-774d54e17126, networkUUID=4e8e5957-649f-477b-9e5b-f1f75b21c03c, name=, ipVersion=4, cidr=10.0.0.0/24, gatewayIP=10.0.0.1, dnsNameservers=[], allocationPools=[NeutronSubnetIPAllocationPool <span class="error">&#91;start=10.0.0.2, end=10.0.0.254&#93;</span>], hostRoutes=[], enableDHCP=true, tenantID=9bacb3c5d39d41a79512987f338cf177, myPorts=[], gatewayIPAssigned=false, ipv6AddressMode=null, ipv6RaMode=null]<br/> 2015-06-03 16:52:32,229 | INFO | qtp736031520-81 | NeutronPortDummyProvider | 258 - org.opendaylight.neutron.dummyprovider - 0.5.0.SNAPSHOT | NeutronPort [portUUID=65c0ee9f-d634-4522-8954-51021b570b0d, networkUUID=4e8e5957-649f-477b-9e5b-f1f75b21c03c, name=private-port, adminStateUp=true, status=DOWN, macAddress=fa:16:3e:c9:cb:f0, fixedIPs=[Neutron_IPs</p> {ipAddress='10.0.0.2', subnetUUID='3b80198d-4f7b-4f77-9ef5-774d54e17126'} <p>], deviceID=, deviceOwner=, tenantID=9bacb3c5d39d41a79512987f338cf177, floatingIPMap={}, securityGroups=<span class="error">&#91;NeutronSecurityGroup{securityGroupUUID=&#39;null&#39;, securityGroupName=&#39;null&#39;, securityGroupDescription=&#39;null&#39;, securityGroupTenantID=&#39;null&#39;, securityRules=null&#93;</span>], bindinghostID=, bindingvnicType=normal, bindingvnicType=normal]<br/> )</p> <p>I have chased this back... and here's what I've found.</p> <p>OpenDaylight is not getting tenant_id in this case because our ML2 OpenStack Driver is sending "tenant_id":"".</p> <p>Our ML2 Driver is sending "tenant_id":"" because that's what ML2 is sending to it.</p> <p>ML2 is sending "tenant_id":"" because the neutron cli commands are sending "tenant_id":"" to the OpenStack neutron NB.</p> <p>Which is to say, this looks like its either a bug in the neutron cli commands, or a problem with how they are being used (I honestly don't know which yet).</p> <p>Reopening/Reassigning to external component for tracking</p> <p>I would love to hear from a neutron (openstack) guru on this, but at the time the neutron port created for the floating ip is instantiated, it has no association with any tenants <span class="error">&#91;1&#93;</span>, yet.</p> <p>Once floating ip is created <span class="error">&#91;2&#93;</span> is that tenant id info is available within<br/> neutron, but if you look at <span class="error">&#91;2&#93;</span>, that is still not associated with the neutron port object.</p> <p>Only when internal&lt;-&gt;external ip association happens is that the mapping of<br/> port happens, but there seems to be no neutron port update being sent to ODL.</p> <p>See this email thread for more info on obtaining this data:</p> <p> <a href="https://lists.opendaylight.org/pipermail/neutron-dev/2015-June/000180.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/neutron-dev/2015-June/000180.html</a></p> <p>===</p> <p><span class="error">&#91;1&#93;</span>: example of a neutron port create just before floating ip is created:</p> <p>POST /controller/nb/v2/neutron/ports/<br/> {<br/> "port": {<br/> "binding:host_id": "", <br/> "allowed_address_pairs": [], <br/> "device_owner": "network:floatingip", <br/> "port_security_enabled": false, <br/> "binding:profile": {}, <br/> "fixed_ips": [</p> { "subnet_id": "00289199-e288-464a-ab2f-837ca67101a7", "ip_address": "192.168.111.22" } <p> ], <br/> "id": "01671703-695e-4497-8a11-b5da989d2dc3", <br/> "security_groups": [], <br/> "device_id": "f013bef4-9468-494d-9417-c9d9e4abb97c", <br/> "name": "", <br/> "admin_state_up": true, <br/> "network_id": "7da709ff-397f-4778-a0e8-994811272fdb", <br/> "tenant_id": "", &lt;==== missing tenant id!<br/> "binding:vif_details": {}, <br/> "binding:vnic_type": "normal", <br/> "binding:vif_type": "unbound", <br/> "mac_address": "FA:16:3E:3F:37:BB"<br/> }<br/> }</p> <p>===</p> <p><span class="error">&#91;2&#93;</span>: floating ip creation</p> <p>POST /controller/nb/v2/neutron/floatingips<br/> {<br/> "floatingip": </p> { "floating_network_id": "7da709ff-397f-4778-a0e8-994811272fdb", "router_id": null, "fixed_ip_address": null, "floating_ip_address": "192.168.111.22", "tenant_id": "cde2563ead464ffa97963c59e002c0cf", &lt;=== tenant id provided "status": "ACTIVE", "port_id": null, &lt;=== neutron port id is missing "id": "f013bef4-9468-494d-9417-c9d9e4abb97c" } <p>}</p> <p>===</p> <p><span class="error">&#91;3&#93;</span>: floating ip association</p> <p>PUT /controller/nb/v2/neutron/floatingips/f013bef4-9468-494d-9417-c9d9e4abb97c<br/> {<br/> "floatingip": </p> { "floating_network_id": "7da709ff-397f-4778-a0e8-994811272fdb", "router_id": "e09818e7-a05a-4963-9927-fc1dc6f1e844", "fixed_ip_address": "10.1.0.3", "floating_ip_address": "192.168.111.22", "tenant_id": "cde2563ead464ffa97963c59e002c0cf", "status": "ACTIVE", "port_id": "341ceaca-24bf-4017-9b08-c3180e86fd24", "id": "f013bef4-9468-494d-9417-c9d9e4abb97c" } <p>}</p> <p>Wait...</p> <p>The port is scoped by the network - if the network is not shared, then by definition, the port must be in the same tenant as the network.<br/> In that case, it is possible to infer the port's tenant id value.</p> <p>(In reply to Ryan Moats from comment #5)<br/> &gt; Wait...<br/> &gt; <br/> &gt; The port is scoped by the network - if the network is not shared, then by<br/> &gt; definition, the port must be in the same tenant as the network.<br/> &gt; In that case, it is possible to infer the port's tenant id value.</p> <p>you are correct. In my poor example, this is not a shared network,<br/> so openstack neutron should be able to get the tenant based on the<br/> network.</p> <p>in cases when net is shared, this is a bit harder. It is good to point<br/> out that the attribute referred as "port_id" in the floating ip<br/> object is referring to the neutron port used by the 'fixed' address, not<br/> the 'floating-ip' address.</p> <p>All in all, we are in complete agreement that it should be possible to<br/> have the tenant-id populated &#8211; as long as the network is not shared.</p> <p>tenant_id=''(empty string) is intentionally passed by neutron l3 code.<br/> It seems quick hack. I filed it to sort them out.</p> <p><a href="https://bugs.launchpad.net/neutron/+bug/1464806" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.launchpad.net/neutron/+bug/1464806</a><br/> <a href="https://bugs.launchpad.net/networking-odl/+bug/1464807" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.launchpad.net/networking-odl/+bug/1464807</a></p> <p>As near term work around, tenant_id can deduced from network object.</p> <p>Supplement.<br/> Actually Neutron passes tenant_id as ''(empty string), not UUID.<br/> <a href="http://git.openstack.org/cgit/openstack/neutron/tree/neutron/db/l3_db.py#n924" class="external-link" target="_blank" rel="nofollow noopener">http://git.openstack.org/cgit/openstack/neutron/tree/neutron/db/l3_db.py#n924</a></p> <p>Is this acceptable by ODL side?<br/> Or should it be UUID?</p> <p>No, an empty tenant ID is not acceptable, neutron northbound expects a valid tenant UUID in this field</p> <p>With the merged done by Isaku <span class="error">&#91;1&#93;</span>, I suspect ODL will no longer get<br/> empty tenant id.</p> <p><span class="error">&#91;1&#93;</span>: <a href="https://review.openstack.org/#/c/191471/" class="external-link" target="_blank" rel="nofollow noopener">https://review.openstack.org/#/c/191471/</a></p> <p>A floating-ip port contains tenant-id after this commit <a href="https://review.openstack.org/#/c/191471/" class="external-link" target="_blank" rel="nofollow noopener">https://review.openstack.org/#/c/191471/</a></p> Development External issue ID 3368 External issue URL Rank 0|i02ucv: