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

Test `The Openstack platform should re-use an existing UDP Amphora LoadBalancer when new svc is created on Openshift with the proper annotation` is flaking

XMLWordPrintable

    • +
    • No
    • ShiftStack Sprint 236, ShiftStack Sprint 237
    • 2
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required

      This is a clone of issue OCPBUGS-13030. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-11646. The following is the description of the original issue:

      Description of problem: The test The Openstack platform should re-use an existing UDP Amphora LoadBalancer when new svc is created on Openshift with the proper annotation is flaking and causes some of our jobs to fail.

      It's particularly visible in 4.12-e2e-openstack-csi-manila where the test caused the last 5 runs to fail.

      https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.12-e2e-openstack-csi-manila

      It's also affecting other releases:

      https://search.ci.openshift.org/?search=The+Openstack+platform+should+re-use+an+existing+UDP+Amphora+LoadBalancer+when+new+svc+is+created+on+Openshift+with+the+proper+annotation&maxAge=168h&context=1&type=bug%2Bissue%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

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

      The job is in 4.12 and above.
      

      How reproducible:

      
      

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      
      

      Expected results:

      
      

      Additional info:

      
      

              maandre@redhat.com Martin André
              openshift-crt-jira-prow OpenShift Prow Bot
              Itshak Brown Itshak Brown
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: