<!-- 
RSS generated by JIRA (9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1) at Sat Feb 10 06:02:09 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>[IEC-15] Investigate failing Aggreg test in kube-conformance e2e.test</title>
                <link>https://jira.akraino.org/browse/IEC-15</link>
                <project id="10201" key="IEC">Integrated Edge Cloud</project>
                    <description>&lt;p&gt;Even after bumping the k8s tests to 1.15.x baseline, which includes proper support for the etcd container image selection (previous versions hardcoded an x86 specific image), the Aggregation layer testcase still fails on IEC, for both x86_64 and aarch64 architectures.&lt;/p&gt;

&lt;p&gt;This might be a configuration issue or an incompatible testing suite configuration, but we&apos;re still investigating the exact rootcause.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10517">IEC-15</key>
            <summary>Investigate failing Aggreg test in kube-conformance e2e.test</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="AlexandruAvadanii">Alexandru Avadanii</assignee>
                                    <reporter username="AlexandruAvadanii">Alexandru Avadanii</reporter>
                        <labels>
                            <label>Release_2</label>
                    </labels>
                <created>Mon, 22 Jul 2019 13:41:17 +0000</created>
                <updated>Tue, 18 Feb 2020 14:28:44 +0000</updated>
                            <resolved>Tue, 18 Feb 2020 14:28:44 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="11108" author="cristinapauna" created="Tue, 18 Feb 2020 14:28:40 +0000"  >&lt;p&gt;Using the same k8s version both for the cluster and the tests fixes the issue&lt;/p&gt;</comment>
                            <comment id="10341" author="alexandruavadanii" created="Tue, 30 Jul 2019 15:42:22 +0000"  >&lt;p&gt;Quick update:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;up to and including K8s 1.13, the Aggreg test was &lt;b&gt;not&lt;/b&gt; part of the Conformance suite, hence we never tested it by default, since we used e2e.test from K8s 1.11 or 1.13;&lt;/li&gt;
	&lt;li&gt;the test is failing with K8s 1.13 and 1.14 / kubernetes-cni 0.6.0/0.7.5 on all tested architectures (x86_64, aarch64);&lt;/li&gt;
	&lt;li&gt;the test is passing with K8s 1.15 (1.15.1) / kubernetes-cni 0.7.5;&lt;/li&gt;
	&lt;li&gt;it looks like CNI is not responsible for the issue;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;So, bumping K8s to 1.15 should automatically fix the problem.&lt;/p&gt;

&lt;p&gt;I will continue the investigation a bit, hopefully I can find the exact rootcause.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10221">VAL-8</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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_10105" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i000yv:</customfieldvalue>

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