-
Epic
-
Resolution: Done
-
Normal
-
openshift-4.19
-
None
-
None
-
MicroShift healthcheck in Go
-
To Do
-
Quality / Stability / Reliability
-
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
Not Selected
-
S
-
None
Epic Goal
- Port existing healthcheck script from bash to Go
Why is this important?
- Leverage static typing and compilation to minimize amount of unnoticed errors
- Kubernetes is written in Go, so verifying status of Deployments/DaemonSets/Pods is native to Go
- Better multithreading + improved error gathering
- Capturing output of a command will not require discarding stderr
- Healthcheck implemented in Go as part of `microshift` command will know best what to expect from MicroShift (what should be running, e.g. optional lvms - lvm2 pkg not installed)
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- is documented by
-
USHIFT-4288 Review documents: ./docs/contributor/greenboot.md and ./docs/user/greenboot.md
-
- Closed
-
- relates to
-
USHIFT-1890 On an EC2 machine, greenboot reports Boot Status is RED - Health Check FAILURE!
-
- Closed
-
- links to
(1 links to)