forwardingrules-manager: Flow add with id L3.149652893104203.21.e7914c35-eafe-4208-9f79-9813ffbc7f69.74.2001:db9:cafe:d:0:0:0:0 failed with error [RpcError [message=Group 150070 not present in the config inventory

Description

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-neon/302/odl_1/odl1_karaf.log.gz

Flows fail to install because of a missing group.

2018-09-30T04:29:12,850 | ERROR | nc-exe-120 | FlowForwarder | 368 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.8.0.SNAPSHOT | Flow add with id L3.149652893104203.21.e7914c35-eafe-4208-9f79-9813ffbc7f69.74.2001:db9:cafe:d:0:0:0:0 failed for node Uri{_value=openflow:149652893104203} with error [RpcError [message=Group 150070 not present in the config inventory, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=null]] 2018-09-30T04:29:12,851 | INFO | nc-exe-121 | FlowForwarder | 368 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.8.0.SNAPSHOT | Reading the group from config inventory: 150070 2018-09-30T04:29:12,851 | ERROR | nc-exe-121 | FlowForwarder | 368 - org.opendaylight.openflowplugin.applications.forwardingrules-manager - 0.8.0.SNAPSHOT | Flow add with id L3.18080470920035.21.e7914c35-eafe-4208-9f79-9813ffbc7f69.74.2001:db9:cafe:d:0:0:0:0 failed for node Uri{_value=openflow:18080470920035} with error [RpcError [message=Group 150070 not present in the config inventory, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=null]]

Environment

None

Attachments

1
  • 01 Oct 2018, 03:31 PM

relates to

Activity

Show:

Sridhar Gaddam October 17, 2018 at 6:22 AM

The following patch in Netvirt addresses the issue on the application side - https://git.opendaylight.org/gerrit/#/c/76628/

daya kamath October 4, 2018 at 3:06 AM

this should be looked into by the netvirt ipv6 folks

daya kamath October 4, 2018 at 3:05 AM

agree anil. sam, the fixes pushed for group before flow are wrt the switch, as there is a race condition sometimes which pushes the flow to the switch before the group and the switch rejects that. however, it is the application responsibility to ensure it pushes the group into the config datastore before the flow. the datastore guarantees ordering of the listeners if the applications ensures this. so, for this error, we need to find out whether the application code did not program the group, or whether there was some exception encountered while trying to do the same

Anil Vishnoi October 4, 2018 at 2:41 AM

It will check if the dependent group is already installed on the switch, than it will push the flow, but if the group itself does not exist in the config data store, it can't do anything.

Sam Hague October 4, 2018 at 1:35 AM

I thought there was a fix included in openflowplugin to catch this condition - ofp would wait to push flows if the group wasn't there.

Done

Details

Assignee

Reporter

Labels

Priority

Created October 1, 2018 at 3:32 PM
Updated October 17, 2018 at 6:24 AM
Resolved October 17, 2018 at 6:24 AM