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-123 neutron <p>Upon creating a port and then updating with multiple fixed IPs per subnet, only one is getting reflected in neutron router config DS.</p> <p>openstack command used for creating port with multiple fixed-ips:</p> <p>neutron port-create ext-net --fixed-ip subnet_id=d8c6125a-8d1a-4802-8bfe-d287776c8b41,ip_address=12.12.12.8 --fixed-ip subnet_id=d8c6125a-8d1a-4802-8bfe-d287776c8b41,ip_address=12.12.12.9</p> <p>What get reflected in MDSAL:</p> <p>{<br/> "ports": [<br/> {<br/> "id": "6d8c0b04-f0d5-44d5-bc4d-43e530839e75",<br/> "tenant_id": "3b54ee92f05c4a45a7e8474badb2e3c8",<br/> "network_id": "65ddef7d-0261-4d2d-8c3e-a028bde26695",<br/> "name": "",<br/> "admin_state_up": true,<br/> "status": "ACTIVE",<br/> "mac_address": "FA:16:3E:EA:6E:94",<br/> "fixed_ips": [</p> { "ip_address": "12.12.12.9", "subnet_id": "d8c6125a-8d1a-4802-8bfe-d287776c8b41" } <p> ],<br/> "device_id": "",<br/> "device_owner": "",<br/> "security_groups": [<br/> {<br/> "id": "40ea057d-1549-4727-86ea-4c3e5dcf107c",<br/> "tenant_id": "3b54ee92f05c4a45a7e8474badb2e3c8",<br/> "name": "default",<br/> "description": "Default security group",<br/> "security_group_rules": [<br/> </p> { "id": "1a11c807-e185-40aa-afe3-3696e0f12d64", "tenant_id": "3b54ee92f05c4a45a7e8474badb2e3c8", "direction": "ingress", "ethertype": "IPv6", "remote_group_id": "40ea057d-1549-4727-86ea-4c3e5dcf107c", "security_group_id": "40ea057d-1549-4727-86ea-4c3e5dcf107c" } <p>,<br/> </p> { "id": "40e96508-a362-43f1-97ea-8486ab461bc4", "tenant_id": "3b54ee92f05c4a45a7e8474badb2e3c8", "direction": "egress", "ethertype": "IPv4", "security_group_id": "40ea057d-1549-4727-86ea-4c3e5dcf107c" } <p>,<br/> </p> { "id": "a16611c1-f4e6-4223-b48b-c1b11b8ec6c1", "tenant_id": "3b54ee92f05c4a45a7e8474badb2e3c8", "direction": "ingress", "ethertype": "IPv4", "remote_group_id": "40ea057d-1549-4727-86ea-4c3e5dcf107c", "security_group_id": "40ea057d-1549-4727-86ea-4c3e5dcf107c" } <p>,</p> { "id": "673ca49f-0ba9-4e70-a63c-0b6f4bf4fb5e", "tenant_id": "3b54ee92f05c4a45a7e8474badb2e3c8", "direction": "egress", "ethertype": "IPv6", "security_group_id": "40ea057d-1549-4727-86ea-4c3e5dcf107c" } <p> ]<br/> }<br/> ],<br/> "allowed_address_pairs": [],<br/> "binding:host_id": "",<br/> "binding:vnic_type": "normal",<br/> "binding:vif_type": "unbound",<br/> "binding:vif_details": [<br/> {}<br/> ]<br/> }<br/> ]<br/> }</p> <p>Operating System: All<br/> Platform: All</p> NEUTRON-123

[stable/beryllium]After creating port with multiple fixedIPs resulting in only fixedIP per subnet getting written to MDSAL

Bug Resolved Done Unassigned Suraj Ranjan Fri, 15 Apr 2016 09:50:57 +0000 Tue, 19 Nov 2019 18:33:42 +0000 Fri, 8 Jul 2016 08:58:45 +0000 unspecified northbound-api 0 4 <p>Issue is in neutron-ports.yang:</p> <p> list fixed-ips {<br/> key subnet-id;<br/> leaf subnet-id </p> { type yang:uuid; } <p> leaf ip-address </p> { type inet:ip-address; } <p> }</p> <p>Yang model allows only one ip-address per subnet. It should be leaf-list, at very list.</p> <p>Yes, neutron API allows for port to have multiple ip addresses from single subnets.</p> <p>Does the following change work?<br/> list fixed-ips {<br/> key "subnet-id ip-address"; &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;<br/> leaf subnet-id </p> { type yang:uuid; } <p> leaf ip-address </p> { type inet:ip-address; } <p> }</p> <p>Yes, this would work but will make it difficult to make queries like 'get all fixed IPs for a subnet' as IP would also need to be part of a key given by user/application.</p> <p><a href="http://developer.openstack.org/api-ref-networking-v2.html#listPorts" class="external-link" target="_blank" rel="nofollow noopener">http://developer.openstack.org/api-ref-networking-v2.html#listPorts</a> suggests that change proposed by Isaku is best way to go. I'll confirm it form q-svc.log </p> <p>Refer meeting log for details:<br/> <a href="http://meetings.opendaylight.org/opendaylight-neutron/2016/neutron_northbound/opendaylight-neutron-neutron_northbound.2016-05-11-15.01.log.html" class="external-link" target="_blank" rel="nofollow noopener">http://meetings.opendaylight.org/opendaylight-neutron/2016/neutron_northbound/opendaylight-neutron-neutron_northbound.2016-05-11-15.01.log.html</a></p> <p>This is what we get from OpenStack:<br/> 'fixed_ips': [</p> { 'subnet_id': u'2044aba1-3ff4-401b-a398-1bf92f9692ce', 'ip_address': u'172.16.0.5' } <p>,<br/> </p> { 'subnet_id': u'2044aba1-3ff4-401b-a398-1bf92f9692ce', 'ip_address': u'172.16.0.8' } <p>]</p> <p>So, should be good to just change the key to 'subnet-id ip-address'. I believe such a change may not even be disruptive unless someone is explicitly trying to get individual entry using the key.</p> <p>Fixed by <a href="https://git.opendaylight.org/gerrit/#/c/35839/9" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/35839/9</a><br/> Hence, closing the bug.</p> Development External issue ID 5735 External issue URL Priority Rank 0|i02uun: