Skip to content

Commit d4c3d5c

Browse files
committed
OSDOCS-14377: updates greenboot wait time MicroShift
1 parent 1755ddd commit d4c3d5c

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

modules/microshift-greenboot-health-check-command.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ To run the `microshift healthcheck` command successfully, use the following prer
1717
You can add the following actions to the `microshift healthcheck` command:
1818

1919
* `-v=2` to increase verbosity of the output
20-
* `--timeout="${WAIT_TIMEOUT_SECS}s"` to override default 300s timeout value
20+
* `--timeout="${WAIT_TIMEOUT_SECS}s"` to override default 600s timeout value
2121
* `--namespace `_<namespace>_` to specify the namespace of the workloads
2222
* `--deployments `_<application-deployment>_` to check the readiness of a specific deployment
2323
+

modules/microshift-greenboot-health-check-log.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ boot_indeterminate=0
3030
boot_counter=2
3131
...
3232
...
33-
Waiting 300s for MicroShift service to be active and not failed
33+
Waiting 600s for MicroShift service to be active and not failed
3434
FAILURE
3535
...
3636
...

modules/microshift-greenboot-microshift-health-script.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,6 @@ The `40_microshift_running_check.sh` health check script only performs validatio
3838
[id="validation-wait-period_{context}"]
3939
== Validation wait period
4040

41-
The wait period in each validation is five minutes by default. After the wait period, if the validation has not succeeded, it is declared a failure. This wait period is incrementally increased by the base wait period after each boot in the verification loop.
41+
The wait period in each validation is 10 minutes by default. After the wait period, if the validation has not succeeded, it is declared a failure. This wait period is incrementally increased by the base wait period after each boot in the verification loop.
4242

43-
* You can override the base-time wait period by setting the `MICROSHIFT_WAIT_TIMEOUT_SEC` environment variable in the `/etc/greenboot/greenboot.conf` configuration file. For example, you can change the wait time to three minutes by resetting the value to 180 seconds, such as `MICROSHIFT_WAIT_TIMEOUT_SEC=180`.
43+
* You can override the base-time wait period by setting the `MICROSHIFT_WAIT_TIMEOUT_SEC` environment variable in the `/etc/greenboot/greenboot.conf` configuration file. For example, you can change the wait time to 5 minutes by resetting the value to 300 seconds, such as `MICROSHIFT_WAIT_TIMEOUT_SEC=300`.

0 commit comments

Comments
 (0)