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

egressIP is not applied back to the node that was stopped then restarted on Azure

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Rejected
    • SDN Sprint 229
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      While running automated test case OCP-47033, it consistently failed on Azure at last step, egressIP is not applied back to the node that was stopped then restarted and became up back

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

      4.12.0-0.nightly-2022-12-05-194559 

      How reproducible:

      run automated OCP-47033

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      at last step, after the stopped/restarted node is back up, its egress IP was not applied back to the node

      Expected results:

      at last step, after the stopped/restarted node is back up, its egress IP address should be applied back to the node

      Additional info:

      This problem consistently occurs while running automated OCP-47033, but it does not happen when running the test manually

       

       

       

       

              pdiak@redhat.com Patryk Diak
              jechen@redhat.com Jean Chen
              None
              None
              Anurag Saxena Anurag Saxena
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: