<!-- 
RSS generated by JIRA (9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1) at Sat Feb 10 06:02:10 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-17] [IEC][SEBA] tosca-loader jobs take a long time to complete</title>
                <link>https://jira.akraino.org/browse/IEC-17</link>
                <project id="10201" key="IEC">Integrated Edge Cloud</project>
                    <description>&lt;p&gt;During the installation of seba charts, there are two pods which take a long time to complete. Their purpose is to load Tosca configurations to xos-tosca, and then they should end with status &apos;Completed&apos;.&lt;/p&gt;

&lt;p&gt;These errors affect the virtual aach64 pods in particular, probably due to the lower processing power.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10524">IEC-17</key>
            <summary>[IEC][SEBA] tosca-loader jobs take a long time to complete</summary>
                <type id="10004" iconUrl="https://jira.akraino.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</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="ciprian.barbu.enea">Ciprian Barbu</assignee>
                                    <reporter username="ciprian.barbu.enea">Ciprian Barbu</reporter>
                        <labels>
                            <label>Release_2</label>
                    </labels>
                <created>Fri, 26 Jul 2019 14:51:42 +0000</created>
                <updated>Wed, 8 Apr 2020 12:41:11 +0000</updated>
                            <resolved>Wed, 8 Apr 2020 12:38:48 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="11198" author="ciprian.barbu.enea" created="Wed, 8 Apr 2020 12:41:11 +0000"  >&lt;p&gt;This is old and probably not applicable anymore. In the meantime we have moved to a new version of SEBA and we are targeting baremetal deployments only. This bug was seen especially on virtual PODs.&lt;/p&gt;</comment>
                            <comment id="10316" author="ciprian.barbu.enea" created="Fri, 26 Jul 2019 16:21:26 +0000"  >&lt;p&gt;After a significant amount of time, around 90 minutes, the&#160;seba-seba-services-tosca-loader pod has disappeared.&lt;/p&gt;

&lt;p&gt;Comparing this with a deployment on a baremetal pod (manually installed on arm-pod8), the corresponding pod has status &apos;Completed&apos; on the baremetal pod:&lt;/p&gt;

&lt;p&gt;ubuntu@iec01:~$ kubectl get pods --all-namespaces | grep -e &apos;\&amp;lt;seba&apos;&lt;br/&gt;
default seba-base-kubernetes-tosca-loader-n8tg4 0/1 Completed 5 29h&lt;br/&gt;
default seba-fabric-78b4dc9754-ddllg 1/1 Running 0 29h&lt;br/&gt;
default seba-fabric-crossconnect-5ff47fcff6-t5flp 1/1 Running 0 29h&lt;br/&gt;
default seba-kubernetes-774c8599d8-b262p 1/1 Running 0 29h&lt;br/&gt;
default seba-onos-service-66fb88f5d4-85h75 1/1 Running 0 29h&lt;br/&gt;
default seba-rcord-594f64db8f-v8nw2 1/1 Running 0 29h&lt;br/&gt;
default seba-seba-services-tosca-loader-hc2px 0/1 Completed 5 29h&lt;br/&gt;
default seba-volt-6795df5d74-rv2gn 1/1 Running 0 29h&lt;br/&gt;
ubuntu@iec01:~$ kubectl logs seba-seba-services-tosca-loader-hc2px&lt;br/&gt;
Starting TOSCA loader using httpie version: 0.9.9&lt;br/&gt;
Loading: /opt/tosca/010-fixtures.yaml&lt;br/&gt;
Created models: &lt;a href=&quot;#tech&amp;#39;, &amp;#39;neutron_port_name&amp;#39;, &amp;#39;c_tag&amp;#39;, &amp;#39;siterole#pi&amp;#39;, &amp;#39;next_hop&amp;#39;, &amp;#39;Private&amp;#39;, &amp;#39;siterole#admin&amp;#39;, &amp;#39;device&amp;#39;, &amp;#39;s_tag&amp;#39;, &amp;#39;Public dedicated IPv4&amp;#39;, &amp;#39;Public shared IPv4&amp;#39;&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&apos;bridge&apos;, &apos;MyDeployment&apos;, &apos;siterole#tech&apos;, &apos;neutron_port_name&apos;, &apos;c_tag&apos;, &apos;siterole#pi&apos;, &apos;next_hop&apos;, &apos;Private&apos;, &apos;siterole#admin&apos;, &apos;device&apos;, &apos;s_tag&apos;, &apos;Public dedicated IPv4&apos;, &apos;Public shared IPv4&apos;&lt;/a&gt;&lt;br/&gt;
Loading: /opt/tosca/020-rcord-subscriber-service.yaml&lt;br/&gt;
Created models: &lt;a href=&quot;#rcord&amp;#39;&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&apos;service#rcord&apos;&lt;/a&gt;&lt;br/&gt;
Loading: /opt/tosca/030-volt-service.yaml&lt;br/&gt;
Created models: &lt;a href=&quot;#volt&amp;#39;&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&apos;service#volt&apos;&lt;/a&gt;&lt;br/&gt;
Loading: /opt/tosca/040-fabric-crossconnect-service.yaml&lt;br/&gt;
Created models: &lt;a href=&quot;#fabric-crossconnect&amp;#39;&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&apos;service#fabric-crossconnect&apos;&lt;/a&gt;&lt;br/&gt;
Loading: /opt/tosca/061-onos-service.yaml&lt;br/&gt;
Created models: &lt;a href=&quot;#onos&amp;#39;, &amp;#39;onos_app#segmentrouting&amp;#39;, &amp;#39;onos_app#aaa&amp;#39;, &amp;#39;aaa-config-attr&amp;#39;, &amp;#39;onos_app#sadis&amp;#39;, &amp;#39;onos_app#olt&amp;#39;, &amp;#39;sadis-config-attr&amp;#39;, &amp;#39;onos_app#kafka&amp;#39;, &amp;#39;onos_app#dhcpl2relay&amp;#39;, &amp;#39;onos_app#openflow-base&amp;#39;, &amp;#39;olt-config-attr&amp;#39;, &amp;#39;kafka-config-attr&amp;#39;, &amp;#39;onos_app#netcfghostprovider&amp;#39;, &amp;#39;onos_app#hostprovider&amp;#39;, &amp;#39;onos_app#openflow&amp;#39;&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&apos;service#onos&apos;, &apos;onos_app#segmentrouting&apos;, &apos;onos_app#aaa&apos;, &apos;aaa-config-attr&apos;, &apos;onos_app#sadis&apos;, &apos;onos_app#olt&apos;, &apos;sadis-config-attr&apos;, &apos;onos_app#kafka&apos;, &apos;onos_app#dhcpl2relay&apos;, &apos;onos_app#openflow-base&apos;, &apos;olt-config-attr&apos;, &apos;kafka-config-attr&apos;, &apos;onos_app#netcfghostprovider&apos;, &apos;onos_app#hostprovider&apos;, &apos;onos_app#openflow&apos;&lt;/a&gt;&lt;br/&gt;
Loading: /opt/tosca/070-fabric-service.yaml&lt;br/&gt;
Created models: &lt;a href=&quot;#fabric&amp;#39;&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&apos;service#fabric&apos;&lt;/a&gt;&lt;br/&gt;
Loading: /opt/tosca/300-service-graph.yaml&lt;br/&gt;
Created models: &lt;a href=&quot;#fabric-crossconnect&amp;#39;, &amp;#39;service#volt&amp;#39;, &amp;#39;service_dependency#volt_fabric-crossconnect&amp;#39;, &amp;#39;service#fabric&amp;#39;, &amp;#39;service#onos&amp;#39;, &amp;#39;service_dependency#onos_volt&amp;#39;, &amp;#39;service_dependency#onos-fabric_fabric&amp;#39;, &amp;#39;service_dependency#onos_fabric-crossconnect&amp;#39;, &amp;#39;service#rcord&amp;#39;, &amp;#39;constraints&amp;#39;, &amp;#39;service_dependency#rcord_volt&amp;#39;&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&apos;service#fabric-crossconnect&apos;, &apos;service#volt&apos;, &apos;service_dependency#volt_fabric-crossconnect&apos;, &apos;service#fabric&apos;, &apos;service#onos&apos;, &apos;service_dependency#onos_volt&apos;, &apos;service_dependency#onos-fabric_fabric&apos;, &apos;service_dependency#onos_fabric-crossconnect&apos;, &apos;service#rcord&apos;, &apos;constraints&apos;, &apos;service_dependency#rcord_volt&apos;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="10315" author="ciprian.barbu.enea" created="Fri, 26 Jul 2019 14:54:42 +0000"  >&lt;p&gt;The same happens to the att-workflow-tosca-loader pod:&lt;/p&gt;

&lt;p&gt;ubuntu@iec01:~$ kubectl logs att-workflow-tosca-loader-jxf4v&lt;br/&gt;
Starting TOSCA loader using httpie version: 0.9.9&lt;br/&gt;
Loading: /opt/tosca/010-fixtures.yaml&lt;/p&gt;

&lt;p&gt;http: error: ConnectionError: (&apos;Connection aborted.&apos;, RemoteDisconnected(&apos;Remote end closed connection without response&apos;,)) while doing POST request to URL: &lt;a href=&quot;http://xos-tosca:9102/run&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://xos-tosca:9102/run&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="10314" author="ciprian.barbu.enea" created="Fri, 26 Jul 2019 14:53:49 +0000"  >&lt;p&gt;ubuntu@iec01:~$ kubectl get pods --all-namespaces | grep tosca-loader&lt;br/&gt;
default att-workflow-tosca-loader-jxf4v 1/1 Running 3 2m7s&lt;br/&gt;
default seba-base-kubernetes-tosca-loader-dsdwl 0/1 CrashLoopBackOff 7 22m&lt;br/&gt;
default seba-seba-services-tosca-loader-6bcvz 0/1 CrashLoopBackOff 7 22m&lt;/p&gt;



&lt;p&gt;ubuntu@iec01:~$ kubectl logs seba-seba-services-tosca-loader-6bcvz&lt;br/&gt;
Starting TOSCA loader using httpie version: 0.9.9&lt;br/&gt;
Loading: /opt/tosca/010-fixtures.yaml&lt;/p&gt;

&lt;p&gt;http: error: ConnectionError: (&apos;Connection aborted.&apos;, RemoteDisconnected(&apos;Remote end closed connection without response&apos;,)) while doing POST request to URL: &lt;a href=&quot;http://xos-tosca:9102/run&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://xos-tosca:9102/run&lt;/a&gt;&lt;br/&gt;
ubuntu@iec01:~$ kubectl logs seba-base-kubernetes-tosca-loader-dsdwl&lt;br/&gt;
Starting TOSCA loader using httpie version: 0.9.9&lt;br/&gt;
Loading: /opt/tosca/010-fixtures.yaml&lt;/p&gt;

&lt;p&gt;http: error: ConnectionError: (&apos;Connection aborted.&apos;, RemoteDisconnected(&apos;Remote end closed connection without response&apos;,)) while doing POST request to URL: &lt;a href=&quot;http://xos-tosca:9102/run&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://xos-tosca:9102/run&lt;/a&gt;&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_10105" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0010f:</customfieldvalue>

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