<!-- 
RSS generated by JIRA (9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1) at Sat Feb 10 06:05:06 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>[ROVER-1] Akraino Edge Stack Portal isn&apos;t updating with the correct status under ETE Testing</title>
                <link>https://jira.akraino.org/browse/ROVER-1</link>
                <project id="10302" key="ROVER">Rover</project>
                    <description>&lt;p&gt;After the &quot;Run Tempest&quot; button is selected the action kicks off the process.&#160; From the scriptexecutor.log we can see the Tempest process is running and it runs successfully.&#160; But on the portal, it still shows &quot;In progress&quot;.&#160; &#160;It stays in this state for over 1.5 hrs.&#160; When we click on the &quot;Refresh&quot; button the status change from &quot;&lt;b&gt;&lt;em&gt;In progress&lt;/em&gt;&lt;/b&gt;&quot; to &quot;&lt;em&gt;&lt;b&gt;exception: Problem while executing script problem while executing the script exit code: 1&lt;/b&gt;&lt;/em&gt;&quot;.&#160;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;I will be attaching the scriptexecutor.log file and a screenshot of the portal.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10226">ROVER-1</key>
            <summary>Akraino Edge Stack Portal isn&apos;t updating with the correct status under ETE Testing</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="10000" iconUrl="https://jira.akraino.org/" description="">To Do</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="davidplunkett">David Plunkett</assignee>
                                    <reporter username="rboswell">Roddric Boswell</reporter>
                        <labels>
                    </labels>
                <created>Wed, 17 Apr 2019 13:59:39 +0000</created>
                <updated>Tue, 14 May 2019 17:35:53 +0000</updated>
                                                                                <due>Fri, 19 Apr 2019 00:00:00 +0000</due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="10151" author="davidplunkett" created="Tue, 14 May 2019 17:35:53 +0000"  >&lt;p&gt;This is a compatibility issue between the ETE Tempest test which requires keystone v2 and v3 api support and the Rover/Unicycle deployments which only support keystone v3.&#160; This is a known issue but is not expected to be resolved until after Akraino R1.&lt;/p&gt;</comment>
                            <comment id="10150" author="mh2094" created="Tue, 14 May 2019 17:30:47 +0000"  >&lt;p&gt;This is a know issue that has been discussed on the Rover and Unicycle calls since February.&#160; Tempest does not support keystone v3 APIs in the save-state function that runs before the tempest test start (used to clean up objects created by tempest).&#160; Current Airship/Airship-in-a-bottle code only implements keystone v3.&#160; This will get fixed in the future, but not anytime soon as it is a low priority function at the moment.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="10005" name="Portal-screenshot.docx" size="187823" author="rboswell" created="Wed, 17 Apr 2019 13:58:30 +0000"/>
                            <attachment id="10004" name="scriptexecutor.log" size="5173396" author="rboswell" created="Wed, 17 Apr 2019 13:58:41 +0000"/>
                    </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|i000b3:</customfieldvalue>

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