Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-27387

egressIP is not assigned back to egress node on vSphere after the node is rebooted

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 4.15.z
    • None
    • -
    • Yes
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          egressIP is not assigned back to egress node on vSphere after the node is rebooted

      Version-Release number of selected component (if applicable):

          4.15.0-0.nightly-2024-01-18-050837

      How reproducible:

          

      Steps to Reproduce:

          1. Install a vSphere OVN cluster with 3 worker nodes, run automated OCP-47033 or do the following steps manually
          2. Label all 3 worker nodes egress-assignable=true, configure an egressip object with 3 EIP addresses, each of the 3 EIP addresses should be assigned to a different egress node
          3.  Shut down one of the egress nodes, EIP should have 2 addresses assigned to the other two nodes
          4.  Start the shutdown node again
          

      Actual results:

         After the node is back to be Ready again, the 3rd EIP address is not assigned back to the node

      Expected results:

       After the node is back to be Ready again, the 3rd EIP address should assigned back to the node   

      Additional info:

          must-gather: https://drive.google.com/file/d/1XIVhbrbkHyKWHTPjyvMx7tvDTCmD-uhi/view?usp=sharing

            jtanenba@redhat.com Jacob Tanenbaum
            jechen@redhat.com Jean Chen
            Jean Chen Jean Chen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: