Este contenido no está disponible en el idioma seleccionado.
Chapter 7. 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.
7.1. Checking the status of greenboot health checks Copiar enlaceEnlace copiado en el portapapeles!
You can check the status of greenboot health checks before making changes to the system or while troubleshooting. By using helpful commands to verify that greenboot scripts have finished running.
Procedure
Check the current greenboot health check status by running the following command:
$ systemctl show --property=SubState --value greenboot-healthcheck.servicewhere:
start- Greenboot checks are still running.
exited-
Checks have passed and greenboot has exited. Greenboot runs the scripts in the
green.ddirectory when the system is in a healthy state. failed-
Checks have not passed. Greenboot runs the scripts in the
red.ddirectory when the system is in this state and restarts the system.
Check the numerical exit code of the greenboot health check service by running the following command:
$ systemctl show --property=ExecMainStatus --value greenboot-healthcheck.serviceAn exit code of
0means the health check succeeded. A non-zero exit code means the health check failed.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-statusExample output
Boot Status is GREEN - Health Check SUCCESS