-
Bug
-
Resolution: Done-Errata
-
Major
-
4.18.0
-
Quality / Stability / Reliability
-
False
-
-
2
-
None
-
None
-
None
-
None
-
uShift Sprint 265
-
1
-
None
-
None
-
-
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
- clones
-
OCPBUGS-48742 Raise the default greenboot timeout to minimize false unhealthy system reports
-
- Closed
-
- depends on
-
OCPBUGS-48742 Raise the default greenboot timeout to minimize false unhealthy system reports
-
- Closed
-
- links to
-
RHBA-2025:8127 Red Hat build of MicroShift 4.16.41 bug fix and enhancement update