Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-3271

RF Storage suite flakes on pod name collision

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 255

      Description of problem:

      The storage suite reuses pod manifests with static names between test cases. Because the test cases are executed in the same namespace, the pod from one case may not have been garbage collected prior to the next test case creating the pod.  Pod creation then fails due to name collision.
      
      stderr:
      Error from server (AlreadyExists): error when creating "./assets/reboot/pod-with-pvc.yaml": pods "test-pod" already exists

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

       

      How reproducible:

      Hard to say as it depends on the garbage collection timing.

      Steps to Reproduce:

      1. cd ~/microshift/test
      2. ./bin/scenario.sh create el94-src@storage.sh
      3. ./bin/scenario.sh run el94-src@storage.sh 
      4. If test fails, examine the RF log output.  Cases are not run in a predetermined order, which might affect the likelihood of the flake.

      Actual results:

      Test fails during test case setup due to pod name collision

      Expected results:

      The pod should never fail to create because of a name collision

      Additional info:

      For a recent example, see:

      https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_microshift/3365/pull-ci-openshift-microshift-main-microshift-metal-tests/1796299419029606400/artifacts/microshift-metal-tests/openshift-microshift-e2e-metal-tests/artifacts/scenario-info/el94-src@storage/log.html#s1-s2-t1-k1-k1-k1-k2

              jcope@redhat.com Jon Cope
              jcope@redhat.com Jon Cope
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: