<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:22:56 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>[NETVIRT-981] CSIT Sporadic failures - snat conntrack job failing many tempest scenario tests</title>
                <link>https://jira.opendaylight.org/browse/NETVIRT-981</link>
                <project id="10144" key="NETVIRT">netvirt</project>
                    <description>&lt;p&gt;the snat-conntrack netvirt csit jobs are having trouble with tempest scenario tests&lt;br/&gt;
and have been for some time. recently we have implemented debugs for each&lt;br/&gt;
tempest test before it does it&apos;s cleanup section. this should help narrow down the&lt;br/&gt;
root cause. Our other non snat-conntrack jobs are not seeing this issue.&lt;/p&gt;

&lt;p&gt;example job:&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-ocata-upstream-stateful-snat-conntrack-oxygen/45/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-ocata-upstream-stateful-snat-conntrack-oxygen/45/&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="28714">NETVIRT-981</key>
            <summary>CSIT Sporadic failures - snat conntrack job failing many tempest scenario tests</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <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="aswins">Aswin Suryanarayanan</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                            <label>csit:failures</label>
                            <label>csit:snat-conntrack</label>
                            <label>csit:sporadic</label>
                    </labels>
                <created>Wed, 8 Nov 2017 00:20:13 +0000</created>
                <updated>Thu, 4 Oct 2018 04:21:06 +0000</updated>
                            <resolved>Thu, 4 Oct 2018 04:21:06 +0000</resolved>
                                                    <fixVersion>Oxygen</fixVersion>
                    <fixVersion>Fluorine</fixVersion>
                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="59989" author="jluhrsen" created="Wed, 8 Nov 2017 00:26:12 +0000"  >&lt;p&gt;currently our csit jobs are dying before they can create the log.html files. But, they do create the output.xml&lt;br/&gt;
which can be used locally to create the log.html.&lt;/p&gt;

&lt;p&gt;so, take this file:&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-ocata-upstream-stateful-snat-conntrack-oxygen/45/robot-plugin/output.xml.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-ocata-upstream-stateful-snat-conntrack-oxygen/45/robot-plugin/output.xml.gz&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;then run this command:&lt;/p&gt;

&lt;p&gt;python -m robot.rebot output.xml.gz&lt;/p&gt;

&lt;p&gt;that will create the log.html you can use to look at the debugs&lt;/p&gt;</comment>
                            <comment id="62171" author="shague@redhat.com" created="Fri, 6 Apr 2018 12:10:57 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=aswinsuryan%40gmail.com&quot; class=&quot;user-hover&quot; rel=&quot;aswinsuryan@gmail.com&quot;&gt;aswinsuryan@gmail.com&lt;/a&gt; should we close this and file other bugs specific to the failing test? I think there might be some other tempest test failure bugs for snat-conntrack, so trying to clean up the bug list.&lt;/p&gt;</comment>
                            <comment id="63140" author="shague@redhat.com" created="Fri, 25 May 2018 12:10:28 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=aswins&quot; class=&quot;user-hover&quot; rel=&quot;aswins&quot;&gt;aswins&lt;/a&gt; should we resolve this issue and then keep open specific issues for each failure that still exists?&lt;/p&gt;</comment>
                            <comment id="63144" author="jluhrsen" created="Fri, 25 May 2018 15:06:07 +0000"  >&lt;p&gt;+1&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_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10301"><![CDATA[Normal]]></customfieldvalue>

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

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