Hello Sam, As per my observation group was created/present during VM ping test case and subsequently deleted during Delete Network test case before the tempest. Can someone from application look at this issue why flow is referring to a non-existing group, whether it is a stale flow. We can later work on next steps once we know where problem exists.
Regards, Sunil From: Sam Hague [mailto:[email protected]] Sent: Saturday, September 16, 2017 6:30 PM To: Sunil Kumar G <[email protected]> Cc: N Vivekanandan <[email protected]>; openflowplugin-dev <[email protected]>; Tomáš Slušný <[email protected]>; Swati Udhavrao Niture <[email protected]>; Kiran N Upadhyaya <[email protected]> Subject: Re: CSIT Debugging for bug-7826 Sunil, Swati, what is the next step here? Do we need more debugging in the logs to track where the group is deleted? Other question is it possible the group has not been created yet or is this definitely a case where the group was there and then was deleted? Thanks, Sam On Fri, Sep 15, 2017 at 5:11 AM, Sunil Kumar G <[email protected]<mailto:[email protected]>> wrote: Hello, From the test logs, I could analyze from these statements: revision=2013-08-19)group/group[{(urn:opendaylight:flow:inventory?revision=2013-08-19)group-id=210004}] does not exist. Cannot apply modification to its children. TransactionCommitFailedException{message=Data did not pass validation., errorList=[RpcError [message=Data did not pass validation., severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node are due to group might have been deleted which the flow might be referring { "barrier": false, "cookie": 141562762, "flow-name": "e9ed8652-6c76-4d7b-a646-b013a2b25e48", "hard-timeout": 0, "id": "525002false", "idle-timeout": 0, "installHw": true, "instructions": { "instruction": [ { "order": 0, "write-actions": { "action": [ { "group-action": { "group-id": 210004 }, "order": 0 } ] } } ] }, "match": { "metadata": { "metadata": 83919634432, "metadata-mask": 1099494850561 } }, "priority": 5, "strict": false, "table_id": 52 }, We can analyze further on what are these stale flows that are existing and what is the action(edit/delete) performed on the flow to hit the situation/exception. Regards, Sunil From: Sam Hague [mailto:[email protected]<mailto:[email protected]>] Sent: Wednesday, September 13, 2017 9:53 PM To: Sunil Kumar G <[email protected]<mailto:[email protected]>>; N Vivekanandan <[email protected]<mailto:[email protected]>>; openflowplugin-dev <[email protected]<mailto:[email protected]>>; Tomáš Slušný <[email protected]<mailto:[email protected]>> Subject: CSIT Debugging for bug-7826 Sunil, pushed a couple jobs below that include the extra debugging for dumping the operational inventory. [1] is the full test suite and [2] is just the tempest tests. The test in the full suite which sporadically has the issue is: Starting test Add Interfaces To Router. Just about any test in the tempest suite hits the issue. Example link to the inventory dump: https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-ocata-upstream-stateful-carbon/125/log.html.gz#s1-s1-s2-t12-k3-k2-k1-k2-k33 Follow the same patch in the log.html file for the jobs below. To see which test actually hit the error for bug-7826, open the smaller odl1_exception.log: https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-ocata-upstream-stateful-carbon/125/odl1_exception.log.gz. From there search for "ModifiedNodeDoesNotExistException". And then preceding that look for "ROBOT MESSAGE: Starting test " to see what test had the error. From there you jump into the log.html specific test to see the debug info. Thanks, Sam [1] https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-ocata-upstream-stateful-carbon/128 and 130 [2] https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-ocata-upstream-stateful-carbon/129 and 131
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
