Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
unspecified
-
None
-
None
-
Operating System: All
Platform: All
-
3141
Description
After the following sequence of operations is followed, the OVSDB southbound MDSAL stops working.
1. configure an OVS host to have a manager of: ovs-vsctl set-manager ptcp:6640
2. use the OVSDB SB MDSAL to connect to the OVS host via a POST command
- MDSAL config and MDSAL operational look good after this step.
3. on the OVS host, delete the manager: ovs-vsctl del-manager - MDSAL config looks ok (still set as in set #2)
- MDSAL operational looks ok - it's cleared out since the OVS host is 'gone'
4. Delete the OVSDB SB MDSAL config node for the OVS host with a DELETE command - MDSAL config looks ok (cleared out)
5. on the OVS host, set the manager again: ovs-vsctl set-manager ptctp:6640
6. (step #2) - connect to OVS host via a POST command - MDSAL config looks ok
- MDSAL operational is not populated
- OVS host does not show up as connected (ovs-vsct show)
After this point, the SB operational MDSAL is no longer getting populated. Attempting to connect to a different OVS host (e.g. step #2) also does not work.
Attachments
Issue Links
- is duplicated by
-
OVSDB-176 Another variation of bz 3141 - mdsal southbound stops updating after del-manager
- Resolved