이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 3. Updating RPMs manually
You can update MicroShift or Red Hat Device Edge manually using RPMs.
3.1. About updates using RPMs 링크 복사링크가 클립보드에 복사되었습니다!
Updating Red Hat build of MicroShift for non-image-based Red Hat Enterprise Linux (RHEL) systems requires updating the RPMs.
- For patch releases, such as 4.21.1 to 4.21.2, simply update the RPMs.
- For minor-version release updates, add the step of enabling the compatible update repository by 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.2. 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.21.1 to 4.21.2.
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 node, or both. For more information, see the following link:
You cannot downgrade MicroShift with this process. Downgrades are not supported.
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.
Procedure
Update the MicroShift RPMs by running the following command:
$ sudo dnf update microshiftRestart MicroShift by running the following command:
$ sudo systemctl restart microshiftNoteThe greenboot 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.3. 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.18 to 4.20.
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 node, or both. For more information, see the following link:
You cannot downgrade MicroShift with this process. Downgrades are not supported.
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.
Procedure
For all lifecycles, enable the repository for the release you want to update to by running the following command:
$ sudo subscription-manager repos \ --enable rhocp-4.21-for-rhel-9-$(uname -m)-rpms \ --enable fast-datapath-for-rhel-9-$(uname -m)-rpmsFor extended support (EUS) releases, also enable the EUS repositories by running the following command:
$ sudo subscription-manager repos \ --enable rhel-9-for-$(uname -m)-appstream-eus-rpms \ --enable rhel-9-for-$(uname -m)-baseos-eus-rpmsAvoid unintended future updates into an unsupported configuration by locking your operating system version with the following command:
$ sudo subscription-manager release --set=9.6Update the MicroShift RPMs by running the following command:
$ sudo dnf update microshiftReboot the host to apply updates by running the following command:
$ sudo systemctl rebootNoteThe 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-healthcheckCheck the health check logs by running the following command:
$ sudo journalctl -u greenboot-healthcheck