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-71 neutron <p>Related log messages:</p> <p>2015-09-25 16:27:33,090 | TRACE | tp932741097-3022 | NeutronSecurityRuleAware | 314 - org.opendaylight.groupbasedpolicy.neutron-mapper - 0.2.2.SNAPSHOT | canCreateNeutronSecurityRule - NeutronSecurityRule</p> {securityRuleUUID='c77016a8-10ac-4f5d-854e-cb3ae4c58397', securityRuleDirection='ingress', securityRuleProtocol='tcp', securityRulePortMin=20202, securityRulePortMax=20208, securityRuleEthertype='IPv4', securityRuleRemoteIpPrefix='192.168.50.0/24', securityRemoteGroupID=null, securityRuleGroupID='5a816afa-fa86-4575-849c-54cc7e74c247', securityRuleTenantID='60b166c6-a167-4094-a717-149b4ee46413'} <p>2015-09-25 16:27:33,091 | ERROR | tp932741097-3022 | ContainerResponse | 217 - com.sun.jersey.jersey-server - 1.17.0 | The RuntimeException could not be mapped to a response, re-throwing to the HTTP container<br/> java.lang.IllegalArgumentException: Cannot create IpAddress from 192.168.50.0/24<br/> at org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev100924.IpAddressBuilder.getDefaultInstance(IpAddressBuilder.java:41)<br/> at org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev100924.IpAddress.&lt;init&gt;(IpAddress.java:40)<br/> at org.opendaylight.neutron.transcriber.NeutronSecurityRuleInterface.toMd(NeutronSecurityRuleInterface.java:198)<br/> at org.opendaylight.neutron.transcriber.NeutronSecurityRuleInterface.toMd(NeutronSecurityRuleInterface.java:38)<br/> at org.opendaylight.neutron.transcriber.AbstractNeutronInterface.addMd(AbstractNeutronInterface.java:47)<br/> at org.opendaylight.neutron.transcriber.NeutronSecurityRuleInterface.addNeutronSecurityRule(NeutronSecurityRuleInterface.java:137)<br/> at org.opendaylight.neutron.northbound.api.NeutronSecurityRulesNorthbound.createSecurityRules(NeutronSecurityRulesNorthbound.java:229)<span class="error">&#91;243:org.opendaylight.neutron.northbound-api:0.5.2.SNAPSHOT&#93;</span><br/> (...)</p> <p>Operating System: All<br/> Platform: All</p> NEUTRON-71

Valid remote-ip-prefix (e.g. 192.168.50.0/24) sent by neutron security-group-rule-create is not accepted by Neutron northbound API

Bug Resolved Done Unassigned Peter Palmar Mon, 28 Sep 2015 07:58:49 +0000 Thu, 19 Oct 2017 21:25:05 +0000 Tue, 13 Oct 2015 11:23:26 +0000 stable/lithium northbound-api 0 5 <p>remote ip prefix has CIDR format - 192.168.50.0/24</p> <p>but neutron-secgroups.yang has modeled remote ip prefix as:</p> <p>leaf remote-ip-prefix {<br/> type inet:ip-address;<br/> }</p> <p>as you can see type inet:ip-prefix should be used instead of intet:ip-address</p> <p>The patch was merged by <a href="https://git.opendaylight.org/gerrit/#/c/26266/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/26266/</a></p> <p>Can you make sure that your ODL neutron northbound include the patch<br/> and test it with the patch?</p> <p>Verified, it works.</p> Development External issue ID 4363 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02uj3: