<!-- 
RSS generated by JIRA (9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1) at Sat Feb 10 05:53:28 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>Akraino JIRA</title>
    <link>https://jira.akraino.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.5</version>
        <build-number>940005</build-number>
        <build-date>11-04-2023</build-date>
    </build-info>


<item>
            <title>[ELIOT-41] [BluVal-Validation-K8S-Conformance-Testcase-Issue: SIG-APPS]</title>
                <link>https://jira.akraino.org/browse/ELIOT-41</link>
                <project id="10204" key="ELIOT">Edge Lightweight and IoT</project>
                    <description>&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;sig-apps&amp;#93;&lt;/span&gt; Daemon set &lt;span class=&quot;error&quot;&gt;&amp;#91;Serial&amp;#93;&lt;/span&gt; should rollback without unnecessary restarts &lt;span class=&quot;error&quot;&gt;&amp;#91;Conformance&amp;#93;&lt;/span&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="10639">ELIOT-41</key>
            <summary>[BluVal-Validation-K8S-Conformance-Testcase-Issue: SIG-APPS]</summary>
                <type id="10002" iconUrl="https://jira.akraino.org/secure/viewavatar?size=xsmall&amp;avatarId=10318&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.akraino.org/images/icons/priorities/medium.svg">Medium</priority>
                        <status id="10001" iconUrl="https://jira.akraino.org/" description="">Done</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="abhijit_onap">Abhijit Dasgupta</assignee>
                                    <reporter username="abhijit_onap">Abhijit Dasgupta</reporter>
                        <labels>
                    </labels>
                <created>Wed, 28 Aug 2019 11:31:35 +0000</created>
                <updated>Mon, 21 Oct 2019 08:36:07 +0000</updated>
                            <resolved>Mon, 21 Oct 2019 08:35:37 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="10802" author="abhijit_onap" created="Mon, 21 Oct 2019 08:35:17 +0000"  >&lt;p&gt;The test case is passed. &lt;br/&gt;
After consulting with the Validation team, and taking the new blu val test case suite, had to untaint the Master node, as the test case pass case criteria was the k8s cluster should have minimum two nodes with Ready state and also can be scheduled. &lt;/p&gt;

&lt;p&gt;Below is the suggestion from Validation team :- &lt;/p&gt;

&lt;p&gt;Hi Abhijit,&lt;/p&gt;



&lt;p&gt;The test is failing with the error &quot;Conformance test suite needs a cluster with at least 2 nodes&quot;. You can open the sonobuoy archive and check plugins/e2e/results/global/e2e.log for the full log.&lt;/p&gt;

&lt;p&gt;I see that your cluster has 2 nodes, so it&apos;s possible that the issue is with reading the number of the nodes. The code of the test is at &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; and it uses function GetReadySchedulableNodesOrDie() to retrieve the nodes.&lt;/p&gt;

&lt;p&gt;Looking at how the function is implemented &lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt;, it looks like both nodes need to be ready and schedulable. Can you manually verify this is the case?&lt;/p&gt;

&lt;p&gt;In any case, this doesn&apos;t look like it&apos;s a validation issue, more likely it&apos;s an issue with the cluster.&lt;/p&gt;



&lt;p&gt;Thanks,&lt;/p&gt;

&lt;p&gt;Cristina&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://github.com/kubernetes/kubernetes/blob/v1.15.4/test/e2e/apps/daemon_set.go#L386&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/kubernetes/kubernetes/blob/v1.15.4/test/e2e/apps/daemon_set.go#L386&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://github.com/kubernetes/kubernetes/blob/v1.15.4/test/e2e/framework/util.go#L2621&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/kubernetes/kubernetes/blob/v1.15.4/test/e2e/framework/util.go#L2621&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------&lt;/p&gt;


&lt;p&gt;Closing the Jira Ticket&lt;/p&gt;</comment>
                            <comment id="10643" author="abhijit_onap" created="Wed, 9 Oct 2019 11:34:26 +0000"  >&lt;p&gt;Have send mail to Validation team, checking what should be done to fix the issue. &lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10100" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ELIOT-31</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10105" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i001n3:</customfieldvalue>

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