starlingx/docs
Code Issues Proposed changes

Merge "Legacy restore with patches does not trigger patching reboot (dsr8mr3, dsr8mr2+, r9)"

Browse Source
This commit is contained in:
Zuul 2024-07-25 18:28:08 +00:00 committed by Gerrit Code Review
commit a55aff236b
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/backup/kubernetes/restoring-starlingx-system-data-and-storage.rst
View File

@ -135,11 +135,21 @@ conditions are in place:
#. Install network connectivity required for the subcloud.
#. Ensure that the system is at the same patch level as it was when the backup
was taken. On the |AIO-SX| systems, you must manually reinstall any
previous patches. This may include doing a reboot if required.
was taken. **You must manually reinstall any previous patches and reboot the
system** (for reboot-required patches) to prevent restore failures due to
mismatched patch levels.
For steps on how to install patches using the :command:`sw-patch install-local` command, see :ref:`aio_simplex_install_kubernetes_r7`;
``Install Software on Controller-0``.
.. note::
This is mandatory for |AIO-SX| (optimized) deployments. For legacy
patches it is only mandatory if either the exclude_patches
(backup) or skip_patches_restore (restore) flags are used.
It is recommended to restore subclouds only when there is an existing
backup taken at the same patch level as the system controller.
For steps on how to install patches using the :command:`sw-patch install-local`
command, see :ref:`aio_simplex_install_kubernetes_r7`; ``Install Software on Controller-0``.
After the reboot, you can verify that the updates were applied.