mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
17 lines
1.0 KiB
Plaintext
17 lines
1.0 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * microshift_install_get_ready/microshift-greenboot.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-greenboot-updates-workloads_{context}"]
|
|
= Updates and third-party workloads
|
|
|
|
Health checks are especially useful after an update. You can examine the output of greenboot health checks and determine whether the update was declared valid. This health check can help you determine if the system is working properly.
|
|
|
|
Health check scripts for updates are installed into the `/etc/greenboot/check/required.d` directory and are automatically executed during each system start. Exiting scripts with a nonzero status means the system start is declared as failed.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
Wait until after an update is declared valid before starting third-party workloads. If a rollback is performed after workloads start, you can lose data. Some third-party workloads create or update data on a device before an update is complete. Upon rollback, the file system reverts to its state before the update.
|
|
====
|