[TOPOPROCES-83] Output topologies occassionally lack some part of themselves

Thu, 19 Oct 2017 17:02:10 +0000

- - Summary ***
    The output topology may on occassion miss a termination point(s), supporting node(s), or any other item(s).
    This usually results in failing of a system test case.

- - Example ***
    An example can be seen in topoprocessing-csit-verify-1node-topology-operations job run nr. 146 [1].
    The test "Link Computation Aggregation Filtration" failed because the output topology lacked a supporting node.

Log evidence:
Trace evidence of the bug can be seen in the karaf logs.
On line 6737 of the karaf log [2] the output node:2 contains the proper amount of supporting nodes.
However, on line 6752 is the UnderlayTopologyListener processing the node:2 again for no apparent reason, only with the aforementioned supporting-node already missing.

- - Links ***
    [1] https://logs.opendaylight.org/releng/jenkins092/topoprocessing-csit-verify-1node-topology-operations/146/archives/
    [2] https://logs.opendaylight.org/releng/jenkins092/topoprocessing-csit-verify-1node-topology-operations/146/archives/karaf.log.gz

OpenDaylight JIRA

[TOPOPROCES-83] Output topologies occassionally lack some part of themselves