Inconsistent Behavior on Multiple Sequential Gate Set – it’s unclear where the bug is in this sequence, but it is possible to get ODL into an inconsistent state through a set of sets/deletes:

. Set a gate
. Delete the gate with a specific gate delete
. Set the same gate again with the exact same information
. Delete the gate with a specific gate delete
. Set the same gate again with the exact same information –

now the set fails. ODL thinks that the gate already exists, even after deleting the gate. The gate does not show up on the operational status report nor the gate report. According to the REST interface, there are no gates.

However – the behavior described above is not consistent. It is possible to get ODL into a state where the “error” in #3 above was not present. Set 3 gates, delete the gates again, then set again WITH THE EXACT SAME INFORMATION and the sets SUCCEED.

Note: All testing was done on an older ubr7200 series CMTS in the lab. A caveat on the age of the hardware is made here, and it may contribute to some of the artifacts seen here, but it remains that OLD should prevent the bad state that results