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

Hostname CI test may get stuck due to a race condition on restart

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • openshift-4.14.z
    • None
    • None
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 247

      This is a clone of issue USHIFT-2136. The following is the description of the original issue:
      —
      This is a clone of issue USHIFT-2134. The following is the description of the original issue:
      —
      Description of problem:

      Hostname CI test may get stuck due to a race condition on restart caused by a host name change. The problem is that the restart is not immediate and the current system readiness check is not fail proof.

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

      4.15 / 4.16

      How reproducible:

      Occasionally in CI

      Steps to Reproduce:

      1. CI

      Expected results:

      After changing the host name, the test should wait until the microshift service process is actually restarted.

      Additional info:

      https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-ocp-metal-nightly-arm/1741262992097415168 

              eslutsky Evgeny Slutsky
              ggiguash@redhat.com Gregory Giguashvili
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: