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

Cleanup-data test is affected by stuck topolvm image pull

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 246

      Description of problem:

      Cleanup-data test is affected by stuck topolvm image pull 

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

       

      How reproducible:

      Random/flake

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

       

      Additional info:

      Observed on presubmits: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_microshift/2575/pull-ci-openshift-microshift-main-metal-periodic-test/1729939869293088768/artifacts/metal-periodic-test/openshift-microshift-e2e-metal-tests/artifacts/scenario-info/el92-src@osconfig/log.html

After clean-data test purges data and starts MicroShift, greenboot healthcheck fails. Details can be seen in keyword that executes "journalctl -u greenboot-healthcheck.service -o short | tail -c 32000" and in SOS:

openshift-storage          topolvm-controller-75f469bbc6-v7cpr        0/5     PodInitializing   0          6m15s   10.42.0.6         el92-src-osconfig-host1   <none>           <none>

       

              ggiguash@redhat.com Gregory Giguashvili
              pmatusza@redhat.com Patryk Matuszak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: