이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 3. About updating RPMs manually
Updating Red Hat build of MicroShift for non-OSTree systems such as Red Hat Enterprise Linux (RHEL) requires updating the RPMs. For patch releases, such as 4.17.1 to 4.17.2, simply update the RPMs. For minor-version release updates, add the step of enabling the update repository using your subscription manager.
You can back up application data as needed and move the data copy to a secure location when using any update type.
3.1. Applying patch updates using RPMs
Updating MicroShift on non rpm-ostree systems such as Red Hat Enterprise Linux (RHEL) requires downloading then updating the RPMs. For example, use the following procedure to upgrade from 4.17.1 to 4.17.2.
Prerequisites
- The system requirements for installing MicroShift have been met.
- You have root user access to the host.
- The version of MicroShift you have is compatible to upgrade to the version you are preparing to use.
- You have verified that your host operating system is compatible with the version of MicroShift you are preparing to install.
- You have completed a system backup.
You cannot downgrade MicroShift with this process. Downgrades are not supported.
Procedure
Update the MicroShift RPMs by running the following command:
$ sudo dnf update microshift
Restart MicroShift by running the following command:
$ sudo systemctl restart microshift
The system health check runs on this update type, but does not perform any actions. If the update fails, an error message appears with the instruction to check the logs.
3.2. Applying minor-version updates with RPMs
Updating a MicroShift minor version on non rpm-ostree systems such as Red Hat Enterprise Linux (RHEL) requires downloading then updating the RPMs. For example, use the following procedure to update from 4.16 to 4.17.
Keeping component versions in a supported configuration of Red Hat Device Edge can require updating MicroShift and RHEL at the same time. Ensure that your version of RHEL is compatible with the version of MicroShift you are updating to, especially if you are updating MicroShift across two minor versions. Otherwise, you can create an unsupported configuration, break your cluster, or both. For more information, see the Red Hat Device Edge release compatibility matrix.
Prerequisites
- The system requirements for installing MicroShift have been met.
- You have root user access to the host.
- The version of MicroShift you have is compatible to upgrade to the version you are preparing to use.
- You have verified that your host operating system is compatible with the version of MicroShift you are preparing to install.
- You have completed a system backup.
You cannot downgrade MicroShift with this process. Downgrades are not supported.
Procedure
For all lifecycles, enable the repository for your release by running the following command:
$ sudo subscription-manager repos \ --enable rhocp-<x.y>-for-<9>-$(uname -m)-rpms \ 1 --enable fast-datapath-for-<9>-$(uname -m)-rpms 2For extended support (EUS) releases, also enable the EUS repositories by running the following command:
`$ sudo subscription-manager repos \ --enable rhel-<9>-for-x86_64-appstream-eus-rpms \ 1 --enable rhel-<9>-for-x86_64-baseos-eus-rpms` 2Avoid unintended future updates into an unsupported configuration by locking your operating system version with the following command:
$ sudo subscription-manager release --set=<9.4> command. 1- 1
- Replace <9.4> with the major and minor version of your compatible RHEL system.
Update the MicroShift RPMs by running the following command:
$ sudo dnf update microshift
Reboot the host to apply updates by running the following command:
$ sudo systemctl reboot
The system health check runs on this update type, but does not perform any actions. If the update fails, an error message appears with the instruction to check the logs.
Verification
Check if the health checks exited with a successful boot by running the following command:
$ sudo systemctl status greenboot-healthcheck
Check the health check logs by running the following command:
$ sudo journalctl -u greenboot-healthcheck
Additional resources
