This group is locked. No changes can be made to the group while it is locked.
Date
1 - 4 of 4
odl-aaa-authn-mdsal-cluster throwing ConfigSnapshotFailureException on start
Srini Seetharaman
Hi,
Sometimes when I start my karaf with the odl-aaa-authn-mdsal-cluster feature enabled instead of the odl-aaa-authn, I get the following exception. Has anyone seen this? What may be causing this? Sometimes I have seen another exception saying the bundle with AAAEncyptionService hasn't started. 2017-04-24 19:27:10,451 | INFO | Event Dispatcher | HttpServiceFactoryImpl | 61 - org.ops4j.pax.web.pax-web-runtime - 3.2.9 | Binding bundle: [org.opendaylight.aaa.authn-federation_0.4.2.Boron-SR2 [238]] to http service 2017-04-24 19:27:18,719 | INFO | rint Extender: 3 | Activator | 224 - org.opendaylight.aaa.authn-sts - 0.4.2.Boron-SR2 | Attempting to resolve class Proxy3bf6e38e_6c75_46ff_a919_cef51fa6fbd2 through AAAServiceTrackerCustomizer 2017-04-24 19:27:18,737 | INFO | rint Extender: 3 | Activator | 224 - org.opendaylight.aaa.authn-sts - 0.4.2.Boron-SR2 | Attempting to resolve class org.opendaylight.aaa.basic.HttpBasicAuth through AAAServiceTrackerCustomizer 2017-04-24 19:27:18,761 | INFO | tAdminThread #12 | BlueprintBundleTracker | 172 - org.opendaylight.controller.blueprint - 0.5.2.Boron-SR2 | Blueprint container for bundle org.opendaylight.aaa.idmlight_0.4.2.Boron-SR2 [229] was successfully created 2017-04-24 19:29:10,426 | ERROR | config-pusher | ConfigPusherImpl | 131 - org.opendaylight.controller.config-persister-impl - 0.5.2.Boron-SR2 | Failed to apply configuration snapshot: 10-rest-connector.xml(acme-app,acme-app). Config snapshot is not semantically correct and will be IGNORED. for detailed information see enclosed exception. org.opendaylight.controller.config.persist.impl.ConfigPusherImpl$ConfigSnapshotFailureException: Failed to apply config snapshot: 10-rest-connector.xml(acme-app,acme-app) during phase: edit at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.pushConfig(ConfigPusherImpl.java:308)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(ConfigPusherImpl.java:164)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.internalPushConfigs(ConfigPusherImpl.java:129)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.processSingle(ConfigPusherImpl.java:83)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.process(ConfigPusherImpl.java:74)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] at org.opendaylight.controller.config.persist.impl.osgi.ConfigPersisterActivator$2.run(ConfigPersisterActivator.java:131)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] at java.lang.Thread.run(Thread.java:745)[:1.8.0_101] Caused by: org.opendaylight.controller.config.api.ModuleFactoryNotFoundException: ModuleFactory not found for module name: rest-connector-impl at org.opendaylight.controller.config.manager.impl.factoriesresolver.HierarchicalConfigMBeanFactoriesHolder.findByModuleName(HierarchicalConfigMBeanFactoriesHolder.java:61) at org.opendaylight.controller.config.manager.impl.ConfigTransactionControllerImpl.createModule(ConfigTransactionControllerImpl.java:235) at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_101] at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_101] at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)[:1.8.0_101] at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_101] at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_101] at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)[:1.8.0_101] at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)[:1.8.0_101] at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)[:1.8.0_101] at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)[:1.8.0_101] at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)[:1.8.0_101] at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)[:1.8.0_101] at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)[:1.8.0_101] at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)[:1.8.0_101] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)[:1.8.0_101] at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)[:1.8.0_101] at com.sun.jmx.mbeanserver.MXBeanProxy$InvokeHandler.invoke(MXBeanProxy.java:150)[:1.8.0_101] at com.sun.jmx.mbeanserver.MXBeanProxy.invoke(MXBeanProxy.java:167)[:1.8.0_101] at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:258)[:1.8.0_101] at com.sun.proxy.$Proxy34.createModule(Unknown Source)[118:org.opendaylight.controller.config-api:0.5.2.Boron-SR2] at org.opendaylight.controller.config.util.ConfigTransactionJMXClient.createModule(ConfigTransactionJMXClient.java:88)[123:org.opendaylight.controller.config-util:0.5.2.Boron-SR2] at org.opendaylight.controller.config.facade.xml.strategy.MissingInstanceHandlingStrategy.handleMissingInstance(MissingInstanceHandlingStrategy.java:30)[129:org.opendaylight.controller.config-manager-facade-xml:0.5.2.Boron-SR2] at org.opendaylight.controller.config.facade.xml.strategy.AbstractEditConfigStrategy.executeConfiguration(AbstractEditConfigStrategy.java:35)[129:org.opendaylight.controller.config-manager-facade-xml:0.5.2.Boron-SR2] at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.handleMisssingInstancesOnTransaction(ConfigSubsystemFacade.java:253)[129:org.opendaylight.controller.config-manager-facade-xml:0.5.2.Boron-SR2] at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.test(ConfigSubsystemFacade.java:163)[129:org.opendaylight.controller.config-manager-facade-xml:0.5.2.Boron-SR2] at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.executeTests(ConfigSubsystemFacade.java:149)[129:org.opendaylight.controller.config-manager-facade-xml:0.5.2.Boron-SR2] at org.opendaylight.controller.config.facade.xml.ConfigSubsystemFacade.executeConfigExecution(ConfigSubsystemFacade.java:123)[129:org.opendaylight.controller.config-manager-facade-xml:0.5.2.Boron-SR2] at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.executeWithMissingModuleFactoryRetries(ConfigPusherImpl.java:329)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] at org.opendaylight.controller.config.persist.impl.ConfigPusherImpl.pushConfig(ConfigPusherImpl.java:305)[131:org.opendaylight.controller.config-persister-impl:0.5.2.Boron-SR2] ... 6 more
|
|
Ryan Goulding <ryandgoulding@...>
The exception you pasted here isn't caused by AAA failure. I suspect the other exception you are seeing is a bug that we are aware of, but haven't filed yet. I cannot reproduce the bug locally but have seen it on Jenkins, and am querying Stephen Kitt for some guidance as it has to do with karaf4 migration. Regards, Ryan Goulding
On Mon, Apr 24, 2017 at 10:35 PM, Srini Seetharaman <srini.seetharaman@...> wrote: Hi,
|
|
Srini Seetharaman
I forgot to mention - The issue was with Boron-SR2.
toggle quoted messageShow quoted text
On Mon, Apr 24, 2017 at 7:57 PM, Ryan Goulding <ryandgoulding@...> wrote:
The exception you pasted here isn't caused by AAA failure. I suspect the
|
|
Srini Seetharaman
When this happened again, I checked the bundle:list and noticed the following. I don't see any relevant log on why jersey-core has not started. 240 | Active | 80 | 1.0.4 | JSR 353 (JSON Processing) Default Provider | org.glassfish.javax.json 241 | Active | 80 | 1.17.0 | jersey-servlet | com.sun.jersey.servlet 242 | Starting | 80 | 1.17.0 | jersey-core | com.sun.jersey.core 243 | Resolved | 80 | 1.17.0 | jersey-server | com.sun.jersey.jersey-server
On Mon, Apr 24, 2017 at 8:29 PM, Srini Seetharaman <srini.seetharaman@...> wrote: I forgot to mention - The issue was with Boron-SR2.
|
|