ConfigPusher failed on toster config file and stopped new OF plugin to connect switches

I run the Virtualization edition with vtn option and -of13 option.

$ ./run.sh -of13 -virt vtn

Three minutes later, ConfigPusher output the following error messages.
It seemed to me that ConfigPusher failed to set configuration for toaster bundle.

==================== Error messages =================================

2014-05-29 03:11:45.506 EDT [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:toaster="urn:opendaylight:params:xml:ns:yang:controller:config:toaster-provider:impl"> toaster:toaster-provider-impl </type><name>toaster-provider-impl</name><rpc-registry><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type><name>binding-rpc-broker</name> </rpc-registry><data-broker><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-data-broker</type><name>binding-data-broker</name> </data-broker><notification-service><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding"> binding:binding-notification-service </type><name>binding-notification-broker</name> </notification-service> </module><module><type xmlns:kitchen="urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl"> kitchen:kitchen-service-impl </type><name>kitchen-service-impl</name><rpc-registry><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type><name>binding-rpc-broker</name> </rpc-registry><notification-service><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding"> binding:binding-notification-service </type><name>binding-notification-broker</name> </notification-service> </module> </modules><services xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"><service><type xmlns:kitchen="urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl"> kitchen:kitchen-service </type><instance><name>kitchen-service</name><provider>/modules/module[type='kitchen-service-impl'][name='kitchen-service-impl']</provider> </instance> </service> </services> </data> ', capabilities=[urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl?module=kitchen-service-impl&revision=2014-01-31, urn:opendaylight:params:xml:ns:yang:controller:config:toaster-provider:impl?module=toaster-provider-impl&revision=2014-01-31]}

. Expected but not found: [urn:opendaylight:params:xml:ns:yang:controller:config:toaster-provider:impl?module=toaster-provider-impl&revision=2014-01-31, urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl?module=kitchen-service-impl&revision=2014-01-31]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.getOperationServiceWithRetries(ConfigPusher.java:111) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.pushConfigWithConflictingVersionRetries(ConfigPusher.java:87) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.pushConfigs(ConfigPusher.java:69) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$1.run(ConfigPersisterActivator.java:156) ~[na:na]
at java.lang.Thread.run(Thread.java:722) ~[na:1.7.0_15]
Caused by: org.opendaylight.controller.netconf.persist.impl.ConfigPusher$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:toaster="urn:opendaylight:params:xml:ns:yang:controller:config:toaster-provider:impl"> toaster:toaster-provider-impl </type><name>toaster-provider-impl</name><rpc-registry><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type><name>binding-rpc-broker</name> </rpc-registry><data-broker><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-data-broker</type><name>binding-data-broker</name> </data-broker><notification-service><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding"> binding:binding-notification-service </type><name>binding-notification-broker</name> </notification-service> </module><module><type xmlns:kitchen="urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl"> kitchen:kitchen-service-impl </type><name>kitchen-service-impl</name><rpc-registry><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type><name>binding-rpc-broker</name> </rpc-registry><notification-service><type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding"> binding:binding-notification-service </type><name>binding-notification-broker</name> </notification-service> </module> </modules><services xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"><service><type xmlns:kitchen="urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl"> kitchen:kitchen-service </type><instance><name>kitchen-service</name><provider>/modules/module[type='kitchen-service-impl'][name='kitchen-service-impl']</provider> </instance> </service> </services> </data> ', capabilities=[urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl?module=kitchen-service-impl&revision=2014-01-31, urn:opendaylight:params:xml:ns:yang:controller:config:toaster-provider:impl?module=toaster-provider-impl&revision=2014-01-31]}

. Expected but not found: [urn:opendaylight:params:xml:ns:yang:controller:config:toaster-provider:impl?module=toaster-provider-impl&revision=2014-01-31, urn:opendaylight:params:xml:ns:yang:controller:config:kitchen-service:impl?module=kitchen-service-impl&revision=2014-01-31]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.getOperationService(ConfigPusher.java:149) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.getOperationServiceWithRetries(ConfigPusher.java:104) ~[na:na]
... 4 common frames omitted

==================== End =================================

I confirmed that the new OF plugin run in ACTIVE.

osgi> ss openflowplugin
"Framework is launched."

id State Bundle
25 ACTIVE org.opendaylight.openflowplugin_0.0.3.SNAPSHOT
osgi>

However, the new OF plugin did not start to listen for TCP 6633 and 6653 port.

odc180 $ netstat -na | grep 6633
odc180 $ netstat -na | grep 6653
odc180 $

Therefore, OpenFlow switches did not establish OF channel with the controller.
I think that the new OF plugin was not successfully initialized.

I used the latest version of the Virtualization edition on 05/27.

odc180 $ git log -3 --oneline
64e608a Adding extra TCs for RESTCONF
3516960 Uploaded working AD-SAL cluster testcases
9903694 Fix TCP-MD5 config not being included