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

Failure of Greenboot when MICROSHIFT_WAIT_TIMEOUT_SEC set below 50

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-229 - Tech Preview version of MicroShift X86
    • uShift Sprint 233, uShift Sprint 234

      Description of problem:

      Experimenting with different numerical values, I ran into an anomaly. When MICROSHIFT_WAIT_TIMEOUT_SEC set below 50, it appears Greenboot fails.

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

       

      How reproducible:

      100%

      Steps to Reproduce:

      1. Install MicroShift Edge instance with /etc/greenboot/greenboot.conf
      2. Set MICROSHIFT_WAIT_TIMEOUT_SEC 45
      3. Reboot 'systemctl reboot'
      4. Observe journalctl -o cat -u greenboot-healthcheck.service  -b

      Actual results:

      FAILURE
      Script '40_microshift_running_check.sh' FAILURE (exit code '1'). Continuing...
      greenboot-healthcheck.service: Main process exited, code=exited, status=1/FAILURE
      greenboot-healthcheck.service: Failed with result 'exit-code'.
      Failed to start greenboot Health Checks Runner.
      greenboot-healthcheck.service: Triggering OnFailure= dependencies.
      

      Expected results:

      The ostree status:
      * rhel e3a0509c32828a27c1ab5ceca13294e4b408a29ae6a227e3c347c441670e64dc.2
          Version: 9.1
          origin refspec: edge:rhel/9/aarch64/edge
        rhel 22e604f438a22bf7c913d69235de90e4ec1443c41e91681db89630410ad4df94.0 (rollback)
          Version: 9.1
          origin: <unknown origin type>
      Waiting 50s for MicroShift service to be active and not failed
      Waiting 50s for MicroShift API health endpoints to be OK
      Waiting 50s for any pods to be running
      Waiting 50s for pod image(s) from the 'openshift-ovn-kubernetes' namespace to be downloaded
      Waiting 50s for pod image(s) from the 'openshift-service-ca' namespace to be downloaded
      Waiting 50s for pod image(s) from the 'openshift-ingress' namespace to be downloaded
      Waiting 50s for pod image(s) from the 'openshift-dns' namespace to be downloaded
      Waiting 50s for pod image(s) from the 'openshift-storage' namespace to be downloaded Checking pod restart count in the 'openshift-ovn-kubernetes' namespace
      Checking pod restart count in the 'openshift-service-ca' namespace
      Checking pod restart count in the 'openshift-ingress' namespace
      Checking pod restart count in the 'openshift-dns' namespace
      Checking pod restart count in the 'openshift-storage' namespace
      FINISHED
      Script '40_microshift_running_check.sh' SUCCESS
      Running Wanted Health Check Scripts...
      Finished greenboot Health Checks Runner.
      

      Additional info:

      It appears that there is a lower boundary where the script (40_microshift_running_check.sh) does not wait long enough for MicroShift to settle out. Requesting a developer take a look.

              ggiguash@redhat.com Gregory Giguashvili
              rh-ee-dhensel Douglas Hensel
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: