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

Raise the default greenboot timeout to minimize false unhealthy system reports

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.19.0
    • 4.18.0
    • MicroShift
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 2
    • None
    • None
    • None
    • None
    • uShift Sprint 264, uShift Sprint 265
    • 2
    • In Progress
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      Description of problem:

      When a rc.1 boot image is deployed, Greenboot is marking the system as unhealthy, even though MicroShift is running and stable.
      
      Should the system default timeout be increased to 600 seconds ?
      
      
      
      
      [redhat@dhcp-1-235-152 ~]$ microshift version MicroShift Version: 4.18.0~rc.1 Base OCP Version: 4.18.0-rc.1

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

       

      How reproducible:

      100%

      Steps to Reproduce:

      1. Deploy a bootc image.
      2. log in and check out Greenboot logs
      3.
      

      Actual results:

      MicroShift is running, Greenboot is marking the system as unhealthy

      Expected results:

      MicroShift should be running, Greenboot should mark the system as healthy

      Additional info:

      SOS report https://drive.google.com/file/d/10YFamGcDsrngKoImDPbW70_Ua-hcCJNI/view?usp=sharing

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

                Created:
                Updated:
                Resolved: