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

[Backport-4.15] TestAllowedSourceRangesStatus expected the annotation to be reflected in status.allowedSourceRanges flake

XMLWordPrintable

    • Low
    • No
    • 1
    • NE Sprint 255, NE Sprint 256
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A (Internal CI fix)
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-35883. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-35368. The following is the description of the original issue:
      —
      Description of problem:

      TestAllowedSourceRangesStatus test is flaking with the error:

allowed_source_ranges_test.go:197: expected the annotation to be reflected in status.allowedSourceRanges: timed out waiting for the condition

I also notice it sometimes coincides with a TestScopeChange error. It may be related updating LoadBalancer type operations, for example, https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-ingress-operator/978/pull-ci-openshift-cluster-ingress-operator-master-e2e-azure-operator/1800249453098045440

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

      4.17

      How reproducible:

      ~25-50%

      Steps to Reproduce:

      1. Run cluster-ingress-operator TestAllowedSourceRangesStatus E2E tests
2.
3.

      Actual results:

      Test is flaking

      Expected results:

      Test shouldn't flake

      Additional info:

      Example Flake

      Search.CI Link

              gspence@redhat.com Grant Spence
              openshift-crt-jira-prow OpenShift Prow Bot
              Hongan Li Hongan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: