Chapter 3. Checking Greenboot scripts status
To deploy applications or make other changes through the MicroShift API with tools other than kustomize manifests, you must wait until the Greenboot health checks have finished. This ensures that your changes are not lost if Greenboot rolls your rpm-ostree system back to an earlier state.
The greenboot-healthcheck service runs one time and then exits. After Greenboot has exited and the system is in a healthy state, you can proceed with configuration changes and deployments.
3.1. Checking the status of Greenboot health checks
Check the status of Greenboot health checks before making changes to the system or during troubleshooting. You can use any of the following commands to help you ensure that Greenboot scripts have finished running.
Procedure
To see a report of health check status, use the following command:
$ systemctl show --property=SubState --value greenboot-healthcheck.service
-
An output of
startmeans that Greenboot checks are still running. -
An output of
exitedmeans that checks have passed and Greenboot has exited. Greenboot runs the scripts in thegreen.ddirectory when the system is a healthy state. -
An output of
failedmeans that checks have not passed. Greenboot runs the scripts inred.ddirectory when the system is in this state and might restart the system.
-
An output of
To see a report showing the numerical exit code of the service where
0means success and non-zero values mean a failure occurred, use the following command:$ systemctl show --property=ExecMainStatus --value greenboot-healthcheck.service
To see a report showing a message about boot status, such as
Boot Status is GREEN - Health Check SUCCESS, use the following command:$ cat /run/motd.d/boot-status
