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

(egressIP on AWS) Only 13 egressIPs are assigned to egressNode while egressIP capacity should be 14 on AWS after upgrade followed by egressip failover

    XMLWordPrintable

Details

    • No
    • 1
    • OCP VE Sprint 239
    • 1
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      After upgrade from 4.12.11 then egressIP failover, only 13 out of 14 egressIP are assigned to egressNode

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

       

      How reproducible:

       

      Steps to Reproduce:

      1. Configure 15 egressip objects to AWS OVN cluster of 4.12.11, 14 egressIPs should be assigned to egressNode
2. Upgrade the cluster to 4.14 latest nightly build, 14 egressIPs were assigned to egressNode
3. Make a second node as egressNode, reboot first egressNode to cause egressIP failover

      Actual results:

      13 out 14 egressIPs are assigned, and they are still on first egressNode

      Expected results:

      14 out 14 egressIPs should be assigned to the new egressNode

      Additional info:

       

      Attachments

        Activity

          People

            pepalani@redhat.com Periyasamy Palanichamy
            jechen@redhat.com Jean Chen
            Jean Chen Jean Chen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: