<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:25:30 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[NEUTRON-77] Tempest test case failures with floating IP&apos;s</title>
                <link>https://jira.opendaylight.org/browse/NEUTRON-77</link>
                <project id="10145" key="NEUTRON">neutron</project>
                    <description>&lt;p&gt;When the tempest scenario test case was run (test_network_basic_ops.py), couple of failures were seen mostly around Floating IP&apos;s&lt;br/&gt;
 We have a end to end setup with l2 and l3 pings working.We have VM&apos;s created associated to Floating IP&apos;s.&lt;/p&gt;

&lt;p&gt;BUild used -&lt;br/&gt;
 Kilo and Liberty &lt;br/&gt;
 ODL - distribution-karaf-0.4.0-20151020.153447-1732&lt;/p&gt;

&lt;p&gt;Initial configs,&lt;br/&gt;
 neutron net-create test-net&lt;br/&gt;
 neutron subnet-create test-net 10.10.10.0/24 --name testsubnet&lt;br/&gt;
 neutron router-create testrouter&lt;br/&gt;
 neutron router-interface-add testrouter testsubnet&lt;br/&gt;
 neutron net-create ext_network &#8211; --router:external=True&lt;br/&gt;
 neutron subnet-create --allocation-pool start=192.34.0.20,end=192.34.0.30 ext_network 192.34.0.0/24 &#8211; --enable_dhcp=False --name ext_subnet&lt;br/&gt;
 neutron router-gateway-set &quot;$rid&quot; &quot;$extid&quot;&lt;br/&gt;
 nova boot --flavor 1 --image &quot;$image_id&quot; --nic net-id=$netw test_vm&lt;br/&gt;
 neutron floatingip-create ext_network&lt;br/&gt;
 neutron floatingip-associate &quot;$floating_ip_id&quot; &quot;$vm_port_id&quot;&lt;/p&gt;

&lt;p&gt;After the above configs, the floating IP is associated to the VM and accessible via ssh&lt;/p&gt;

&lt;p&gt;Failure 1: test_update_instance_port_admin_state&lt;br/&gt;
 Initially the floating IP is reachable and we can ssh to it.&lt;br/&gt;
 Now we edit the admin_state attribute of instance port to &quot;DOWN&quot;. It is expected that the floating IP should no longer be reachable.&lt;br/&gt;
 However, in our case it is still reachable.&lt;/p&gt;

&lt;p&gt;Failure 2: test_update_router_admin_state&lt;br/&gt;
 Similar to failure 1..In this case the admin_state attribute of the router is set to &quot;DOWN&quot;..&lt;br/&gt;
 Even after this, the Floating IP is reachable.&lt;/p&gt;

&lt;p&gt;Failure 3: test_network_basic_ops&lt;br/&gt;
 Once you disassociate a floating-ip from the VM, the test case verifies that the status of the floating IP shows &quot;DOWN&quot;.&lt;br/&gt;
 In our case it shows as &quot;ACTIVE&quot;. Not sure if this is the expected behavior and the test case needs some change.&lt;br/&gt;
 GET &lt;a href=&quot;http://105.0.1.216:9696/v2.0/floatingips&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://105.0.1.216:9696/v2.0/floatingips&lt;/a&gt;&lt;br/&gt;
 {&lt;br/&gt;
 &quot;floatingip&quot; :&lt;/p&gt;

{ &quot;id&quot; : &quot;a058801b-2c98-4d4d-b90a-505ae2d295e6&quot;, &quot;tenant_id&quot; : &quot;036bcfd5b251416ca35fe2cfa730f433&quot;, &quot;floating_network_id&quot; : &quot;7c1a4760-3c64-43b2-a9d4-f604b95a3bf1&quot;, &quot;floating_ip_address&quot; : &quot;192.34.0.21&quot;, &quot;status&quot; : &quot;ACTIVE&quot; &amp;lt;==== }

&lt;p&gt;}&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Linux&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26639">NEUTRON-77</key>
            <summary>Tempest test case failures with floating IP&apos;s</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="rijilabraham@gmail.com">Rijil Abraham</reporter>
                        <labels>
                    </labels>
                <created>Wed, 28 Oct 2015 06:23:39 +0000</created>
                <updated>Wed, 26 May 2021 10:44:21 +0000</updated>
                            <resolved>Fri, 2 Dec 2016 06:44:30 +0000</resolved>
                                    <version>Multiple</version>
                                                    <component>northbound-api</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="53468" author="yamahata" created="Fri, 2 Dec 2016 06:44:30 +0000"  >&lt;p&gt;now related test cases pass with openstack CI.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4543</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=4543]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02ukf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>