Documentation: backup_restore introduce system restore-complete command
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
M Camp |
Bug Description
Following this hierarchy:
https:/
Restoring¶
Platform restore¶
Steps:
2.Restore:
e. Re-apply applications (e.g. OpenStack) to force pods to restart.
Replace existing step `e.` with this:
e. Wait for Calico and Coredns pods to start. Run `system restore-complete` command. Type 750.006 alarms will disappear one at a time, as the apps are being auto applied.
Explanation: The `system restore-complete` command was introduced by this commit: https:/
-------
Following this hierarchy:
https:/
Restoring¶
Platform restore¶
Steps:
2.Restore:
d. After Ansible is executed, perform the following steps based on your deployment mode:
For each of the 4 lab types after the first step (the step A, describing the unlock of controller-0) introduce a new step:
B. Apps should transition from 'restore-requested' to 'applying' state, then from 'applying' state to 'applied' state. If apps are transitioned from 'applying' to 'restore-requested' state, ensure there is network access and access to the docker registry. Once per minute the process is repeated until all apps are transitioned to 'applied'.
Explanation: Logic changed by this commit: https:/
tags: | added: stx.5.0 |
Thanks Dan for submitting this LP, I will be sure the docs are updated and CC you on the review.