[OVSDB-67] OVSDB SFC Issues when starting controller Created: 05/Sep/14  Updated: 02/Mar/15  Resolved: 02/Mar/15

Status: Resolved
Project: ovsdb
Component/s: Other
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Dave Tucker Assignee: Sam Hague
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: PC


External issue ID: 1722
Priority: High

 Description   

2014-09-05 19:44:41.667 BST [config-pusher] ERROR o.o.c.l.b.i.UncaughtExceptionPolicy - Thread Thread[config-pusher,5,main] died because of an uncaught exception
java.lang.IllegalStateException: Max wait for capabilities reached.Not enough capabilities for ConfigSnapshot

{configSnapshot='<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"><module><type xmlns:ovssfc="urn:opendaylight:params:xml:ns:yang:controller:config:ovssfc-provider:impl"> ovssfc:ovssfc-provider-impl </type><name>ovssfc-provider-impl</name><data-broker><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type><name>binding-data-broker</name> </data-broker> </module> </modules> </data> ', capabilities=[urn:opendaylight:params:xml:ns:yang:controller:config:ovssfc-provider:impl?module=ovssfc-provider-impl&revision=2014-06-30, urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding?module=opendaylight-md-sal-binding&revision=2013-10-28]}

. Expected but not found: [urn:opendaylight:params:xml:ns:yang:controller:config:ovssfc-provider:impl?module=ovssfc-provider-impl&revision=2014-06-30]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:158) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(ConfigPusherImpl.java:134) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.internalPushConfigs(ConfigPusherImpl.java:111) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.process(ConfigPusherImpl.java:78) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$1.run(ConfigPersisterActivator.java:178) ~[na:na]
at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_55]
Caused by: org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl$NotEnoughCapabilitiesException: Not enough capabilities for ConfigSnapshot

{configSnapshot='<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"><module><type xmlns:ovssfc="urn:opendaylight:params:xml:ns:yang:controller:config:ovssfc-provider:impl"> ovssfc:ovssfc-provider-impl </type><name>ovssfc-provider-impl</name><data-broker><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type><name>binding-data-broker</name> </data-broker> </module> </modules> </data> ', capabilities=[urn:opendaylight:params:xml:ns:yang:controller:config:ovssfc-provider:impl?module=ovssfc-provider-impl&revision=2014-06-30, urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding?module=opendaylight-md-sal-binding&revision=2013-10-28]}

. Expected but not found: [urn:opendaylight:params:xml:ns:yang:controller:config:ovssfc-provider:impl?module=ovssfc-provider-impl&revision=2014-06-30]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationService(ConfigPusherImpl.java:196) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:151) ~[na:na]
... 5 common frames omitted



 Comments   
Comment by Sam Hague [ 24/Sep/14 ]

The error log does indicate a problem, but it isn't harmful.

The error log comes out because the ovssfc bundle is not loaded when running virt "-virt ovsdb". Config processes the ovssfc config file and then looks for the corresponding service to handle the capabilities it found in the file.

karaf does not have this problem because the ovssfc config file is only loaded when the ovssfc feature is requested and the bundle is also loaded.

I haven't found a method yet to not include the config file when -virt ovsdb is used via run.sh

Comment by Sam Hague [ 02/Mar/15 ]

This was only an issue in the pre-karaf distributions. Only karaf will be used going forward so there is no need to fix this issue.

Generated at Wed Feb 07 20:35:25 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.