Uploaded image for project: 'mdsal'
  1. mdsal
  2. MDSAL-197

Switch connection bounce results in wrong ownership change in Singleton

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Done
    • None
    • None
    • None
    • None
    • Operating System: Linux
      Platform: All

    • 6710

    Description

      In Carbon, sometimes, when switch is disconnected and reconnected with very small delay between these actions, it's role is incorrectly set (should be MASTER, but is SLAVE).

      Reproduction steps (from Luis from bug https://bugs.opendaylight.org/show_bug.cgi?id=6672):
      1) start mininet 1 switch (s1) pointing to any of the cluster instances (e.g. 10.13.11.207)
      2) Run the following script in the mininet system to bounce connection quickly:

      #!/bin/bash
      sudo ovs-vsctl del-controller s1
      sleep 0.2
      sudo ovs-vsctl set-controller s1 "tcp:192.168.0.101"

      In local cluster test, I did step 2 twice. First time, role MASTER was successfully set, but second time, role was SLAVE, what is incorrect.

      I attached logs from my local testing from node 10.13.11.207.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              vdemcak@cisco.com Vaclav Demcak
              tomas.slusny@pantheon.tech Tomas Slusny
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: