第 4 章 Updating RPMs manually
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.16.1 to 4.16.2, simply update the RPMs. For minor-version release updates, add the step of enabling the 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.
4.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.16.1 to 4.16.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 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
Update the MicroShift RPMs by running the following command:
$ sudo dnf update 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.