<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:03:57 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>[INTPAK-224] Support and test ansible-odl deployments will all defaults vars</title>
                <link>https://jira.opendaylight.org/browse/INTPAK-224</link>
                <project id="10190" key="INTPAK">integration-packaging</project>
                    <description>&lt;p&gt;The current design of the ansible-opendaylight test logic is such that there is a builder/script that is meant to apply ODL with all default vars, then run tests. A second builder/script runs serially to override some default&#160;param and run tests again.&lt;/p&gt;

&lt;p&gt;However, the default buildr/script still uses a playbook that overrides the default rpm_repo_url var. That result in verify jobs always testing that version of ODL, not whatever version the actual defaults point to. This is evident when changing the defaults, like in &lt;a href=&quot;https://jira.opendaylight.org/browse/INTPAK-223&quot; title=&quot;Updates for Fluorine SR1&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INTPAK-223&quot;&gt;&lt;del&gt;INTPAK-223&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Should add test coverage that actually uses all default vars.&lt;/p&gt;

&lt;p&gt;Update: Discovered while adding test coverage that the rpm_repo_url var we always override is actually broken out of the box. See comments for details. Re-scoped this issue to cover.&lt;/p&gt;</description>
                <environment></environment>
        <key id="31111">INTPAK-224</key>
            <summary>Support and test ansible-odl deployments will all defaults vars</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="3" iconUrl="https://jira.opendaylight.org/images/icons/statuses/inprogress.png" description="This issue is being actively worked on at the moment by the assignee.">In Progress</status>
                    <statusCategory id="4" key="indeterminate" colorName="yellow"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="linux_geek">Taseer Ahmed</assignee>
                                    <reporter username="dfarrell07">Daniel Farrell</reporter>
                        <labels>
                    </labels>
                <created>Tue, 27 Nov 2018 01:52:24 +0000</created>
                <updated>Mon, 10 Dec 2018 17:56:43 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="65772" author="dfarrell07" created="Tue, 27 Nov 2018 02:29:38 +0000"  >&lt;p&gt;Add playboks that don&apos;t override rpm_repo_url, including one that still installs REST API so we can switch to that in tests:&#160;&lt;a href=&quot;https://git.opendaylight.org/gerrit/78186&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/78186&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="65773" author="dfarrell07" created="Tue, 27 Nov 2018 02:37:40 +0000"  >&lt;p&gt;Switch ansible-odl RPM tests to default ODL vers: &lt;a href=&quot;https://git.opendaylight.org/gerrit/78187&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/78187&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="65816" author="dfarrell07" created="Thu, 29 Nov 2018 04:30:39 +0000"  >&lt;p&gt;Well, this is interesting. Running with the two changes so far in the sandbox, I&apos;m seeing a failure:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;TASK &lt;span class=&quot;error&quot;&gt;&amp;#91;opendaylight : Download ODL yum repo cfg file&amp;#93;&lt;/span&gt; ***************************&lt;br/&gt;
fatal: &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost&amp;#93;&lt;/span&gt;: FAILED! =&amp;gt; {&quot;msg&quot;: &quot;The task includes an option with an undefined variable. The error was: Unable to look up a name or access an attribute in template string (&lt;/p&gt;
&lt;div class=&quot;error&quot;&gt;&lt;span class=&quot;error&quot;&gt;Unknown macro: {% if &amp;#39;latest_release&amp;#39; not in odl_version %}&lt;/span&gt; &lt;/div&gt;
&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/gitweb?p=integration/packaging.git;a=blob_plain;f=packages/rpm/example_repo_configs/opendaylight-&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/gitweb?p=integration/packaging.git;a=blob_plain;f=packages/rpm/example_repo_configs/opendaylight-\&lt;/a&gt;{{ odl_version_dict&lt;span class=&quot;error&quot;&gt;&amp;#91;odl_version&amp;#93;&lt;/span&gt; }}-devel.repo{% else %}&lt;a href=&quot;https://git.opendaylight.org/gerrit/gitweb?p=integration/packaging.git;a=blob_plain;f=packages/rpm/example_repo_configs/opendaylight-9-release.repo&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/gitweb?p=integration/packaging.git;a=blob_plain;f=packages/rpm/example_repo_configs/opendaylight-9-release.repo\&lt;/a&gt;{% endif %}).\n&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&quot;https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/ansible-test-rpm-master/1/console.log.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/ansible-test-rpm-master/1/console.log.gz&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I think what&apos;s going on is that we always override rpm_repo_url in CI, so some contributions from the OPNFV XCI folks introduced vars here that work in there env but don&apos;t work in an all-defaults deployment. I remember being worried about this at the time but not having proper CI coverage to validate myself.&lt;/p&gt;

&lt;p&gt;I think we might need to simplify that default var, at the expense of potentially requiring some changes from OPNFV folks.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="31109">INTPAK-223</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03kzj:</customfieldvalue>

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