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

Services may fail to restart in tests due to unplanned reboots or frequent restart attempts

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 2
    • None
    • None
    • uShift Sprint 245
    • None
    • None
    • None

      Description of problem:

      Services are configured to allow 5 restarts within 10s.
      
      $ sudo systemctl show greenboot-healthcheck.service | grep StartLimit
      StartLimitIntervalUSec=10s
      StartLimitBurst=5
      StartLimitAction=none
      
      Also, we need to make sure that tests wait for greenboot checks to complete successfully before manipulating MicroShift service status. This may cause Greenboot to detect invalic microshift status and reboot the host

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

      4.15

      How reproducible:

      Occasionally fails in CI depending on the order of the executed tests (random).

      Steps to Reproduce:

      1.Examine the output of CI jobs
      

      Actual results:

      Services fails to restart and spurrious boots happen sometimes

      Expected results:

      Services should allow restarts and no spurrious boots should occur

      Additional info:

      https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-ocp-metal-nightly-arm/1728217145898176512/artifacts/ocp-metal-nightly-arm/openshift-microshift-e2e-metal-tests/artifacts/scenario-info/el92-src@osconfig/log.html

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

                Created:
                Updated:
                Resolved: