https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-149 netconf <p><a href="https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-only-beryllium/1085/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-only-beryllium/1085/</a><br/> <a href="https://jenkins.opendaylight.org/releng/job/capwap-csit-1node-ac-only-beryllium/649" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/capwap-csit-1node-ac-only-beryllium/649</a><br/> <a href="https://jenkins.opendaylight.org/releng/job/netconf-csit-1node-userfeatures-only-beryllium/201/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/netconf-csit-1node-userfeatures-only-beryllium/201/</a><br/> <a href="https://jenkins.opendaylight.org/releng/job/usc-csit-1node-channel-only-beryllium/926/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/usc-csit-1node-channel-only-beryllium/926/</a></p> <p>trace from log (full log of one example attached)</p> <p>2016-02-13 13:44:54,516 | ERROR | config-pusher | ConfigPusherImpl | 108 - org.opendaylight.controller.config-persister-impl - 0.4.0.Beryllium | Failed to apply configuration snapshot: 01-netconf.xml(odl-netconf-client,odl-netconf-client)<br/> java.lang.IllegalStateException: Unable to resolve value AttributeConfigElement [defaultValue=null, value=MappedDependency</p> {namespace='urn:opendaylight:params:xml:ns:yang:controller:netty', serviceName='netty-threadgroup', refName='global-worker-group'} <p>] to attribute worker-thread-group<br/> at org.opendaylight.controller.config.facade.xml.mapping.config.InstanceConfig.resolveConfiguration(InstanceConfig.java:131)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.InstanceConfig.fromXml(InstanceConfig.java:192)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.ModuleConfig.fromXml(ModuleConfig.java:59)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.Config$1.resolveElement(Config.java:147)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.Config$1.resolveElement(Config.java:144)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.Config.resolveModule(Config.java:224)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.Config.fromXmlModulesResolved(Config.java:152)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.ConfigExecution.getResolvedXmlElements(ConfigExecution.java:49)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.setOnTransaction(ConfigSubsystemFacade.java:228)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.test(ConfigSubsystemFacade.java:165)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.executeTests(ConfigSubsystemFacade.java:149)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.executeConfigExecution(ConfigSubsystemFacade.java:123)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.executeWithMissingModuleFactoryRetries(ConfigPusherImpl.java:329)<span class="error">&#91;108:org.opendaylight.controller.config-persister-impl:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.pushConfig(ConfigPusherImpl.java:305)<span class="error">&#91;108:org.opendaylight.controller.config-persister-impl:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(ConfigPusherImpl.java:164)<span class="error">&#91;108:org.opendaylight.controller.config-persister-impl:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.internalPushConfigs(ConfigPusherImpl.java:129)<span class="error">&#91;108:org.opendaylight.controller.config-persister-impl:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.processSingle(ConfigPusherImpl.java:83)<span class="error">&#91;108:org.opendaylight.controller.config-persister-impl:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.process(ConfigPusherImpl.java:74)<span class="error">&#91;108:org.opendaylight.controller.config-persister-impl:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.persist.impl.osgi.ConfigPersisterActivator$2.run(ConfigPersisterActivator.java:131)<span class="error">&#91;108:org.opendaylight.controller.config-persister-impl:0.4.0.Beryllium&#93;</span><br/> at java.lang.Thread.run(Thread.java:745)<span class="error">&#91;:1.7.0_85&#93;</span><br/> Caused by: java.lang.IllegalArgumentException: No service mapped to urn:opendaylight:params:xml:ns:yang:controller:netty:netty-threadgroup:global-worker-group. Wrong namespace, available namespaces: <span class="error">&#91;urn:opendaylight:params:xml:ns:yang:controller:threadpool, urn:opendaylight:params:xml:ns:yang:controller:netconf:topology:shared:schema:repository, urn:opendaylight:params:xml:ns:yang:controller:shutdown, urn:opendaylight:params:xml:ns:yang:controller:config:netconf&#93;</span><br/> at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145)<span class="error">&#91;51:com.google.guava:18.0.0&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.ServiceRegistryWrapper.getByServiceAndRefName(ServiceRegistryWrapper.java:32)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.attributes.resolving.ObjectNameAttributeResolvingStrategy.parseAttribute(ObjectNameAttributeResolvingStrategy.java:44)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.attributes.fromxml.AttributeConfigElement.resolveValue(AttributeConfigElement.java:46)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.config.facade.xml.mapping.config.InstanceConfig.resolveConfiguration(InstanceConfig.java:127)<span class="error">&#91;106:org.opendaylight.controller.config-manager-facade-xml:0.4.0.Beryllium&#93;</span><br/> ... 19 more</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-149

Beryllium RC3: some CSIT jobs aborting. IllegalStateException when loading odl-netconf-client

Bug Verified Done Tomas Cere Jamo Luhrsen Sat, 13 Feb 2016 16:45:46 +0000 Fri, 15 Mar 2019 22:22:20 +0000 Wed, 17 Feb 2016 16:47:23 +0000 netconf 0 6 <p>sorry, I do not have a full karaf.log. The console output from one of jobs is attached which gives the first and last 500K bytes. Note, there are a ton of AuthenticationExceptions, but those are expected as it's our polling on restconf by our bringup script</p> <p>Attachment 5346.karaf.log.gz has been added with description: first and last 500K bytes of karaf.log</p> <p>These failures do not happen with Beryllium snapshot builds, but they do not happen when testing RC3 on Sandbox <span class="error">&#91;0&#93;</span> either.</p> <p>Common denominator is netconf connector. The jobs either install odl-netconf-connector-all (in job definition), or they install odl-netconf-connector (via odl-usc-channel).</p> <p>The error message mentions odl-netconf-client feature, while global-worker-group is defined in 00-netty.xml config file of odl-config-netty feature (which is not listed as dependency of odl-netconf-client).</p> <p>Probably, the 00-netty.xml is pulled in by some other feature being installed, and it depends on system performance whether ODL detects the transient inconsistency or not.</p> <p>Change 34675 <span class="error">&#91;1&#93;</span> contributed to address the dependency issue, but there may be more hidden issues of this type, see comments of <a href="https://jira.opendaylight.org/browse/ODLPARENT-12" title="SingleFeatureTest : Can it verify also requirements from config files?" class="issue-link" data-issue-key="ODLPARENT-12"><del>ODLPARENT-12</del></a>.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://jenkins.opendaylight.org/sandbox/job/netconf-csit-1node-userfeatures-only-beryllium/1" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/netconf-csit-1node-userfeatures-only-beryllium/1</a><br/> <span class="error">&#91;1&#93;</span> <a href="https://git.opendaylight.org/gerrit/34675" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/34675</a></p> <p>Thanks Vratko!</p> <p>Is this related? </p> <p>&gt; 2016-02-13 13:44:49,924 | INFO | Event Dispatcher | YangTextSchemaContextResolver | 69 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.Beryllium | Provided module name /META-INF/yang/threadpool.yang@0000-00-00.yang does not match actual text threadpool@2013-04-09.yang, corrected</p> <p>&gt; <a href="https://git.opendaylight.org/gerrit/34675" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/34675</a></p> <p><a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-only-beryllium/206" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-only-beryllium/206</a><br/> is queued and it shall verify this Change does not break snapshot builds.</p> <p>But I do not see an easy way to verify its supposed effect on autorelease builds, without actually making new autorelease build with the Change merged.</p> <p>&gt; Is this related? </p> <p>No, that is a warning from new Yangtools parser, after the automatic source name conversion everything works.</p> <p>This means we are re-spinning the release right?</p> <p>there are other "ready-to-submit" patches out there as well.</p> <p>This means we are re-spinning the release right?</p> <p>there are other "ready-to-submit" patches out there as well.</p> <p>&gt; we are re-spinning the release right?</p> <p>+1</p> <p>Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Beryllium without it? Is there a workaround such that we can write a release note and fix in Beryllium SR1?<br/> Testing: Could you also elaborate on the testing or this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests? <br/> Impact: Does this fix impact any dependent projects?</p> <p>(In reply to A H from comment #10)<br/> &gt; Severity: Could you elaborate on the severity of this bug? Is this a<br/> &gt; BLOCKER such that we cannot release Beryllium without it? Is there a<br/> &gt; workaround such that we can write a release note and fix in Beryllium SR1?</p> <p>I don't know of any workaround, but I didn't really look. IMO this is a<br/> release blocker as it prevents restconf from coming up when specific<br/> user facing features are installed.</p> <p>&gt; Testing: Could you also elaborate on the testing or this patch? How<br/> &gt; extensively has this patch been tested? Is it covered by any unit tests or<br/> &gt; system tests?</p> <p>There are the four system test jobs (initial comment) that will give us<br/> good confidence that the patch gets us past this bug.</p> <p>&gt; Impact: Does this fix impact any dependent projects?</p> <p>not sure. Hopefully Vratko can add more info here.</p> <p>(In reply to Jamo Luhrsen from comment #11)<br/> &gt; (In reply to A H from comment #10)<br/> &gt; &gt; Severity: Could you elaborate on the severity of this bug? Is this a<br/> &gt; &gt; BLOCKER such that we cannot release Beryllium without it? Is there a<br/> &gt; &gt; workaround such that we can write a release note and fix in Beryllium SR1?<br/> &gt; <br/> &gt; I don't know of any workaround, but I didn't really look. IMO this is a<br/> &gt; release blocker as it prevents restconf from coming up when specific<br/> &gt; user facing features are installed.<br/> &gt; <br/> &gt; &gt; Testing: Could you also elaborate on the testing or this patch? How<br/> &gt; &gt; extensively has this patch been tested? Is it covered by any unit tests or<br/> &gt; &gt; system tests?<br/> &gt; <br/> &gt; There are the four system test jobs (initial comment) that will give us<br/> &gt; good confidence that the patch gets us past this bug.</p> <p>I would also agree that the four CSIT that failed would cover the testing aspects of this patch.</p> <p>&gt; &gt; Impact: Does this fix impact any dependent projects?<br/> &gt; <br/> &gt; not sure. Hopefully Vratko can add more info here.</p> <p>This fix would impact projects whose CSIT jobs failed originally. We will know more once we rerun these jobs after merging the fix.</p> <p>&gt; Could you elaborate on the severity of this bug?</p> <p>When user installs a feature related to netconf-connector, ODL may break so that even basic Restconf does not work. This is a blocker unless a workaround is applied.</p> <p>&gt; How extensively has this patch been tested?</p> <p>This Bug is not reproducible on Sandbox or on Snapshot builds, probably because a timing issue. The Bug was reproduced on Releng with original autorelease build. <br/> The fix was only proven to not make things worse. Even when it improves the code, next respin may fail on similar issue in other parts of code.</p> <p>&gt; Is there a workaround such that we can write a release note and fix in Beryllium SR1?</p> <p>If user installs odl-config-netty feature prior anything related to netconf-connector, ODL should work.<br/> Due to difficulties with reproducing this Bug, it is not clear whether this workaround indeed works.</p> <p>&gt; Is it covered by any unit tests or system tests?</p> <p>No specific system tests, apart the 4 csit jobs that were reported.<br/> No unit tests for this Bug exist right now. Comments in <a href="https://jira.opendaylight.org/browse/ODLPARENT-12" title="SingleFeatureTest : Can it verify also requirements from config files?" class="issue-link" data-issue-key="ODLPARENT-12"><del>ODLPARENT-12</del></a> may enable creation of such unit tests, but probably not before Beryllium Release.</p> <p>&gt; Does this fix impact any dependent projects?</p> <p>No, projects were already expecting netconf-connector to install all its dependencies.</p> <p>The bgpcep job triggered with autorelease URL on RelEng Jenkins works again <span class="error">&#91;0&#93;</span>.<br/> Setting to FIXED.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-only-beryllium/1094/console" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-only-beryllium/1094/console</a></p> <p>Have we been able to verify the fix for this bug?</p> <p>(In reply to A H from comment #15)<br/> &gt; Have we been able to verify the fix for this bug?</p> <p>using the CSIT jobs with RC3 we can mark this verified.</p> Development External issue ID 5346 External issue URL Rank 0|i01wrb: