The following hostconfig related WARN and ERROR karaf logs keeps showing after we executed ovs-vsctl set-manager in Controller Node and Compute Node.
We checked ODL operational datastore, the hostconfig information shows successfully.
- 2017-10-31 15:38:11,169 | WARN | rd-dispatcher-32 | ShardDataTree | 214 - org.opendaylight.controller.sal-distributed-datastore - 1.6.0 | member-1-shard-default-operational: Store Tx member-1-datastore-operational-fe-0-txn-53-0: Conflicting modification for path /(urn:opendaylight:neutron?revision=2015-07-12)neutron/hostconfigs/hostconfig/hostconfig[\{(urn:opendaylight:neutron?revision=2015-07-12)host-id=nitrogen-controller, (urn:opendaylight:neutron?revision=2015-07-12)host-type=ODL L2}].
2017-10-31 15:38:11,170 | WARN | ult-dispatcher-8 | ConcurrentDOMDataBroker | 214 - org.opendaylight.controller.sal-distributed-datastore - 1.6.0 | Tx: DOM-190 Error during phase CAN_COMMIT, starting Abort
OptimisticLockFailedException {message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]] at org.opendaylight.controller.cluster.datastore.ShardDataTree.lambda$processNextPendingTransaction$0(ShardDataTree.java:731)[214:org.opendaylight.controller.sal-distributed-datastore:1.6.0] ...... 2017-10-31 15:38:11,170 | ERROR | lt-dispatcher-21 | LocalThreePhaseCommitCohort | 214 - org.opendaylight.controller.sal-distributed-datastore - 1.6.0 | Failed to prepare transaction member-1-datastore-operational-fe-0-txn-53-0 on backend OptimisticLockFailedException\{message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]]}at
org.opendaylight.controller.cluster.datastore.ShardDataTree.lambda$processNextPendingTransaction$0(ShardDataTree.java:731)[214:org.opendaylight.controller.sal-distributed-datastore:1.6.0]
......
2017-10-31 15:38:11,188 | WARN | eChangeHandler-0 | MdsalUtils | 363 - org.opendaylight.ovsdb.utils.mdsal-utils - 1.5.0 | Failed to put KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.neutron.hostconfig.rev150712.hostconfig.attributes.hostconfigs.Hostconfig, path=[org.opendaylight.yang.gen.v1.urn.opendaylight.neutron.rev150712.Neutron, org.opendaylight.yang.gen.v1.urn.opendaylight.neutron.hostconfig.rev150712.hostconfig.attributes.Hostconfigs, org.opendaylight.yang.gen.v1.urn.opendaylight.neutron.hostconfig.rev150712.hostconfig.attributes.hostconfigs.Hostconfig[key=HostconfigKey [_hostId=nitrogen-controller, _hostType=ODL L2]]]}
OptimisticLockFailedException{message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]]}
at
org.opendaylight.controller.cluster.datastore.ShardDataTree.lambda$processNextPendingTransaction$0(ShardDataTree.java:731)[214:org.opendaylight.controller.sal-distributed-datastore:1.6.0]
at
org.opendaylight.controller.cluster.datastore.ShardDataTree.processNextPending(ShardDataTree.java:769)[214:org.opendaylight.controller.sal-distributed-datastore:1.6.0]
.....
- relates to
-
OVSDB-455 l2 agent marked down when no response to http://172.16.0.15:8081/restconf/operational/neutron:neutron/hostconfigs
- Open