starlingx/docs
Code Issues Proposed changes
docs/doc/source/updates/kubernetes/patch-release-deployment-before-bootstrap-and-commissioning-of-7d0a97144db8.rst
Juanita Balaraj 2dbaaba94a Added Appendix for USM Updates 
Updated patchset 7 comments
Added --local to command ``sudo software upload --local <patch-release>.patch**``
Fixed line break
Reverted Index and only added the Appendix - Kubernetes Platform for this Gerrit review, see https://review.opendev.org/c/starlingx/docs/+/923472;
https://review.opendev.org/c/starlingx/docs/+/923747 for Index updates.
Reverted Index updates as per Patchset 3 comments
- Reorganized Kubernetes Version Upgrade section
- Moved N3000 information to the Appendix (Deperecated)

Story: 2010676
Task: 50141
Change-Id: I5b08427567b2cd98516a109c113655ad946fba89
Signed-off-by: Juanita Balaraj <juanita.balaraj@windriver.com>
2024-08-30 20:40:26 +00:00

3.5 KiB
Raw Blame History

Deployment of Patch Releases before Bootstrap and Commissioning of initial Installation

When initially installing a system, occassionally it is required to deploy the latest available patch release for the major release being deployed.

The patch releases should be deployed using the procedure below.

  • AFTER the intial install of software on the first host (controller-0), and
  • BEFORE running the Ansible Bootstrap Playbook and configuring and installing software on any other hosts.

This ensures that:

  • The software on controller-0, and all other hosts, is up to date when the cluster first becomes active.
  • You reduce installation time by avoiding having to patch the system right after an out-of-date software installation is completed.

  • The software patch releases that are required to be deployed are available on a USB flash drive, or from a server reachable by controller-0.
  • You are at the beginning of a system installation. Specifically,
    • You have used the bootable ISO image (for a major release) to install the software on controller-0.
    • You have logged into the console port as user sysadmin, BUT you have NOT bootstrapped the system yet.

  1. Upload the patch releases.

    Upload the updates from the USB flash drive using the software upload <patch-release.patch file> command.

    Note

    sudo is required for authentication due to authentication not currently running.

    $ sudo software upload --local <patch-release>.patch**
<release-id> is now uploaded
+-------------------------------+-------------------+
| Uploaded File                  | Release          |
+-------------------------------+-------------------+
| <new-release>.patch            | <new-release-id> |
+-------------------------------+-------------------+

    Note

    Repeat the above command for all patch releases to be deployed.

  2. If you copied the patch release file(s) to /home/sysadmin/, then remove these files.

    After the patch release files are uploaded to the system, the original files are no longer required.

    You should delete them to ensure enough disk space to complete the installation.

    Caution

    If the original files are not deleted before the updates are applied, the installation may fail due to a full disk.

  3. Deploy the patch releases.

    $ sudo software deploy start
<highest-patch-release-id-being-deployed>

$ sudo software deploy localhost

Patch Release deployment complete.
Please reboot before continuing.

  4. Reboot controller-0.

    You must reboot the controller to ensure that it is running with the software fully updated.

    $ sudo reboot

Continue with bootstrapping and configuring your system.

Once all hosts in the cluster are initialized, they will all be running fully patched software.