Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-51198

Greenboot Fail Marker not removed on ostree deployments

XMLWordPrintable

    • None
    • 1
    • uShift Sprint 267
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: Restarting failed greenboot-healthcheck without rebooting a system
      *Consequence*: Greenboot healthcheck for MicroShift optional components will continue failing
      *Fix*: Primary microshift greenboot healthcheck clears the condition that would cause optional components' healthchecks to fail
      *Result*: Bug doesn’t present anymore.
      Show
      *Cause*: Restarting failed greenboot-healthcheck without rebooting a system *Consequence*: Greenboot healthcheck for MicroShift optional components will continue failing *Fix*: Primary microshift greenboot healthcheck clears the condition that would cause optional components' healthchecks to fail *Result*: Bug doesn’t present anymore.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-51184. The following is the description of the original issue:
      —
      Description of problem:

      There was an expectation that upon failed greenboot, the host will be rebooted so the /run/microshift-greenboot-healthcheck-failed is removed, but this expectation doesn't play nicely with non-ostree deployments...

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

      4.18.1

      How reproducible:

      Always

      Steps to Reproduce:

      1. Run RF osconfig/clusterid.robot Suite on a ostree deployment
2.
3.

      Actual results:

      https://jenkins-csb-openshift-qe-mastern.dno.corp.redhat.com/job/microshift/job/microshift-rf-tests/5098/

      Expected results:

       

      Additional info:

      https://redhat-internal.slack.com/archives/C03CJTNLKAT/p1740395237897719

              pmatusza@redhat.com Patryk Matuszak
              openshift-crt-jira-prow OpenShift Prow Bot
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: