[OVSDB-152] OVSDB southbound operational MDSAL stops getting populated after ovs-vsctl del-manager Created: 06/May/15  Updated: 22/Jun/15  Resolved: 22/Jun/15

Status: Resolved
Project: ovsdb
Component/s: Southbound.Open_vSwitch
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Eric Multanen Assignee: Sharad Mishra
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
is duplicated by OVSDB-176 Another variation of bz 3141 - mdsal ... Resolved
External issue ID: 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.

 Comments   
Comment by Anil Vishnoi [ 06/May/15 ]

quick clarification .. i assume "ptcpt:6640" is typo in step 5?

5. on the OVS host, set the manager again: ovs-vsctl set-manager ptctp:6640

Even though it's not valid connection type, but ovsdb will set it up anyways for you and that can cause issues.

Comment by Eric Multanen [ 06/May/15 ]

yes - that was a typo. should be ptcp:6640

Comment by Sam Hague [ 11/Jun/15 ]

https://git.opendaylight.org/gerrit/#/c/22404/

Generated at Wed Feb 07 20:35:38 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.