Uploaded image for project: 'ovsdb'
  1. ovsdb
  2. OVSDB-286

ovs node removed from operational after partitioned from network and a config is made

    XMLWordPrintable

Details

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

    • 5178

    Description

      the final result is an ovs instance thinking it's connected to the plugin (e.g. "is_connected: true") but it does not exist in operational.

      steps to reproduce:

      1. connect ovs node to plugin (ovs-vsctl set-manager)

      2. partition node from controller with iptables:
      sudo /sbin/iptables -A OUTPUT -p tcp --dport 6640 -j DROP

      3. clear ip tables so communication is ok again.

      4. create a bridge via northbound rest api

      notes:

      It doesn't appear that the plugin times out the connected node when it
      stops hearing from it (between steps 2 and 3). I've let it sit for many
      minutes like this and it remains in operational.

      after step 3, the plugin throws an exception because the node connecting
      again "was already registered for ownership"

      after step 4, the plugin removes the node because it "has no owner, cleaning up the operational data store"

      full karaf log attached

      Attachments

        1. 5178.karaf.log
          118 kB
        2. karaf.log
          221 kB
        3. karaf.log-1
          476 kB
        4. Steps_toreproduce.txt
          9 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            ananthip@hcl.com Ananthi Palaniswamy
            jluhrsen Jamo Luhrsen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: