<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:19 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>[CONTROLLER-1349] Typo in unrelated config file can block netconf-connector functionality</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1349</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;The severity of the resulting buggy state may be caused by some other component, but config subsystem should filter out the triggering condition of this bug.&lt;/p&gt;

&lt;p&gt;This description uses PCEP as the component with config files unrelated to netconf connector.&lt;/p&gt;

&lt;p&gt;Steps to reproduce:&lt;br/&gt;
0. Download an unpack a recent Lithium snapshot build with otherwise working netconf connector.&lt;br/&gt;
1. start ODL&lt;br/&gt;
2. feature:install odl-restconf-noauth odl-bgpcep-pcep-all odl-netconf-connector-all&lt;br/&gt;
3. wait few minutes to make sure netconf-connector had time to start&lt;br/&gt;
4. curl -s 127.0.0.1:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules&lt;br/&gt;
5. see all modules configured as intended&lt;br/&gt;
6. kill ODL java process&lt;br/&gt;
7. rm -rf data/ snapshots/ journal/ lock idmlight.db.mv.db&lt;br/&gt;
8. edit etc/opendaylight/karaf/39-pcep-provider.xml value in line 52, from &quot;stateful07&quot; to &quot;stateful06&quot;.&lt;br/&gt;
9. - 12. repeat steps 1. - 4.&lt;br/&gt;
13. see {&quot;errors&quot;:{&quot;error&quot;:[&lt;/p&gt;
{&quot;error-type&quot;:&quot;protocol&quot;,&quot;error-tag&quot;:&quot;unknown-element&quot;,&quot;error-message&quot;:&quot;Mount point does not exist.&quot;}
&lt;p&gt;]}}&lt;/p&gt;

&lt;p&gt;Alternative to step 3: monitor karaf.log till you see netconf-connector success message.&lt;br/&gt;
Alternative to step 11: monitor karaf.log, see it stops scrolling forever just after Leader moves node to &lt;span class=&quot;error&quot;&gt;&amp;#91;Up&amp;#93;&lt;/span&gt;.&lt;/p&gt;

&lt;p&gt;The only interesting log I see buried in such step 11 is this:&lt;br/&gt;
2015-05-29 09:50:46,959 | WARN  | r - ConfigPusher | FeatureConfigPusher              | 132 - config-persister-feature-adapter - 0.3.0.SNAPSHOT | Karaf featuresService.listInstalledFeatures() has not yet finished installing feature (retry 0) odl-bgpcep-pcep-all 0.4.0-SNAPSHOT&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25903">CONTROLLER-1349</key>
            <summary>Typo in unrelated config file can block netconf-connector functionality</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="vrpolak">Vratko Polak</reporter>
                        <labels>
                    </labels>
                <created>Fri, 29 May 2015 10:11:08 +0000</created>
                <updated>Thu, 19 Oct 2017 21:26:45 +0000</updated>
                            <resolved>Wed, 5 Jul 2017 00:52:46 +0000</resolved>
                                    <version>Post-Helium</version>
                                                    <component>config</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="50760" author="mmarsale@cisco.com" created="Mon, 1 Jun 2015 08:30:58 +0000"  >&lt;p&gt;Postponing for Beryllium. This needs to be thought through a bit more and theres not much time for Lithium left.&lt;/p&gt;

&lt;p&gt;ConfigPusher halts its execution after a semantic failure(in an initial config) by design. With current implementation, this would be possible, but very confusing in case of a failed config for core services or services that are dependencies for others. Also whats the point of trying to spawn user services if the core has already failed... &lt;/p&gt;

&lt;p&gt;If ConfigPusher knew whats critical config snapshot and whats not, it could possibly ignore the semantic failures in non critical snapshots at least.&lt;/p&gt;</comment>
                            <comment id="50761" author="vrpolak" created="Wed, 17 Jun 2015 09:27:32 +0000"  >&lt;p&gt;Current behavior in Lithium is that semantic error stops config subsystem (this bug), but syntactic error makes config subsystem to just ignore the offending configfile and continue as if nothing happened (as verified in &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-922&quot; title=&quot;Errors in feature config files are not reported enough&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-922&quot;&gt;&lt;del&gt;CONTROLLER-922&lt;/del&gt;&lt;/a&gt;). One of the behavior should be changed.&lt;/p&gt;

&lt;p&gt;As resolution of this bug is postponed, I have created improvement &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1372&quot; title=&quot;Semantic errors in feature config files could be reported better&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1372&quot;&gt;&lt;del&gt;CONTROLLER-1372&lt;/del&gt;&lt;/a&gt; to at least log that an error has happened.&lt;/p&gt;</comment>
                            <comment id="50762" author="vrpolak" created="Thu, 5 Nov 2015 14:38:12 +0000"  >&lt;p&gt;Change 28985 was merged to lithium (not Beryllium yet).&lt;br/&gt;
That implementation does not stops the whole karaf, but it still stops pushing configs upon first failure, preventing unrelated configs to be applied.&lt;/p&gt;</comment>
                            <comment id="50763" author="tpantelis" created="Wed, 5 Jul 2017 00:52:46 +0000"  >&lt;p&gt;Not sure what the ask is here but the CSS is being deprecated so not worth addressing.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="25077">CONTROLLER-523</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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3430</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=3430]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10349"><![CDATA[Unspecified]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02q0v:</customfieldvalue>

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