-
Bug
-
Resolution: Done
-
None
-
Lithium
-
None
-
Operating System: All
Platform: All
-
4703
During SR3 system test runs, one of the jobs failed to bring "UP" the controller
which is determined by receiving a 200 response from /restconf/modules within
10 minutes.
re-running the job [0] was ok and the system test passed.
filing this bug now in the hopes that more info and repro steps can be determined in order to fix and prevent this kind of problem.
full karaf log is attached, but the brief trace is here:
2015-11-24 07:20:42,528 | ERROR | config-pusher | ConfigPusherImpl | 108 - org.opendaylight.controller.config-persister-impl - 0.3.3.Lithium-SR3 | Unable to push configuration due to missing yang models. Yang models that are missing, but required by the configuration: [urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:impl?module=opendaylight-sal-binding-broker-impl&revision=2013-10-28, urn:opendaylight:params:xml:ns:yang:controller:inmemory-datastore-provider?module=opendaylight-inmemory-datastore-provider&revision=2014-06-17]. For each mentioned model check: 1. that the mentioned yang model namespace/name/revision is identical to those in the yang model itself 2. the yang file is present in the system 3. the bundle with that yang file is present in the system and active 4. the yang parser did not fail while attempting to parse that model
2015-11-24 07:20:42,528 | ERROR | config-pusher | ConfigPusherImpl | 108 - org.opendaylight.controller.config-persister-impl - 0.3.3.Lithium-SR3 | Failed to apply configuration snapshot: 01-md-sal.xml(odl-dlux-core,odl-dlux-core)
java.lang.IllegalStateException: Unable to push configuration due to missing yang models. Required yang models that are missing: [urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:impl?module=opendaylight-sal-binding-broker-impl&revision=2013-10-28, urn:opendaylight:params:xml:ns:yang:controller:inmemory-datastore-provider?module=opendaylight-inmemory-datastore-provider&revision=2014-06-17]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:180)[108:org.opendaylight.controller.config-persister-impl:0.3.3.Lithium-SR3]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(ConfigPusherImpl.java:143)[108:org.opendaylight.controller.config-persister-impl:0.3.3.Lithium-SR3]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.internalPushConfigs(ConfigPusherImpl.java:106)[108:org.opendaylight.controller.config-persister-impl:0.3.3.Lithium-SR3]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.process(ConfigPusherImpl.java:77)[108:org.opendaylight.controller.config-persister-impl:0.3.3.Lithium-SR3]
at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$1.run(ConfigPersisterActivator.java:181)[108:org.opendaylight.controller.config-persister-impl:0.3.3.Lithium-SR3]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_85]
Caused by: org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl$NotEnoughCapabilitiesException: Not enough capabilities for 01-md-sal.xml(odl-dlux-core,odl-dlux-core). Expected but not found: [urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:impl?module=opendaylight-sal-binding-broker-impl&revision=2013-10-28, urn:opendaylight:params:xml:ns:yang:controller:inmemory-datastore-provider?module=opendaylight-inmemory-datastore-provider&revision=2014-06-17]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationService(ConfigPusherImpl.java:260)[108:org.opendaylight.controller.config-persister-impl:0.3.3.Lithium-SR3]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:163)[108:org.opendaylight.controller.config-persister-impl:0.3.3.Lithium-SR3]
... 5 more
[0] https://jenkins.opendaylight.org/releng/job/ovsdb-csit-1node-netvirt-all-stable-lithium