Uploaded image for project: 'controller'
  1. controller
  2. CONTROLLER-1527

Entity Ownership cannot be reacquired after 3-nodes cluster recovers

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Cannot Reproduce
    • Beryllium
    • None
    • clustering
    • None
    • Operating System: All
      Platform: All

    • 6092

    Description

      In a 3-node cluster when 2 of the nodes are shut down, the remain node got stuck with the ownership of the Entity after the entity is de-registered and registered.

      Steps to reproduce,
      1. Bring up a 3 node cluster
      2. Set the managers of an OVS device to all 3 nodes in the cluster. This should result in a candidate registering for each node in the cluster.
      3. Now let's say member-2 is the owner of the OVS connection entity
      4. Kill the controller process for both member-1 and member-2.
      5. Now the member-3 is owner of connection entity
      6. Delete the managers of the OVS node
      7. Re-set the managers of an OVS device to all 3 nodes in the cluster.
      8. Restart the 2 nodes for member-1 and member-2
      9. Delete and set manager of the OVS node.

      Issue: there is no ownershipChanged event to the DeviceEntityOwnershipListener as result of Connection entity deregistered and re-registered

      Attachments

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

        Activity

          People

            Unassigned Unassigned
            vinh.nguyen@hcl.com Vinh Nguyen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: