Chapter 3. Updating RPMs on an OSTree system
Updating MicroShift on an rpm-ostree system such as Red Hat Enterprise Linux for Edge (RHEL for Edge) requires building a new RHEL for Edge image containing the new version of MicroShift and any associated optional RPMs. After you have the rpm-ostree image with MicroShift embedded, direct your system to boot into that operating system image.
The procedures are the same for minor-version and patch updates. For example, use the same steps to upgrade from 4.14 to 4.16 or from 4.16.0 to 4.16.1.
Red Hat Device Edge release compatibility matrix
Red Hat Enterprise Linux (RHEL) and MicroShift work together as a single solution for device-edge computing. You can update each component separately, but the product versions must be compatible. For example, an update of MicroShift from 4.14 to 4.16 requires a {op-system} update. Supported configurations of Red Hat Device Edge use verified releases for each together as listed in the following table:
| RHEL for Edge Version(s) | MicroShift Version | MicroShift Release Status | Supported MicroShift Version→MicroShift Version Updates |
| 9.4 | 4.16 | Generally Available | 4.16.0→4.16.z, 4.14→4.16 and 4.15→4.16 |
| 9.2, 9.3 | 4.15 | Generally Available | 4.15.0→4.15.z, 4.14→4.15 and 4.15→4.16 |
| 9.2, 9.3 | 4.14 | Generally Available | 4.14.0→4.14.z, 4.14→4.15 and 4.14→4.16 |
| 9.2 | 4.13 | Technology Preview | None |
| 8.7 | 4.12 | Developer Preview | None |
Downgrades are not supported. The following procedure is for upgrades only.
3.1. Applying updates on an OSTree system
To update MicroShift on an rpm-ostree system such as Red Hat Enterprise Linux for Edge (RHEL for Edge), embed the new version of MicroShift on a new operating system image. The steps you use depends on how your existing deployment is set up. The following procedure outlines the general steps you can take, with links to the RHEL for Edge documentation. The RHEL for Edge documentation is your resource for specific details on building an updated operating system image. Back up and system rollback are automatic with this update type.
You can also use this workflow to update applications running in the MicroShift cluster. Ensure compatibility between the application and the adjacent versions of MicroShift and RHEL for Edge before starting an update.
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 with the RHEL for Edge image you are preparing to use.
You cannot downgrade MicroShift with this process. Downgrades are not supported.
Procedure
Create an Image Builder configuration file for adding the
rhocp-4.16RPM repository source required to pull MicroShift RPMs by running the following command:$ cat > rhocp-4.16.toml <<EOF id = "rhocp-4.16" name = "Red Hat OpenShift Container Platform 4.16 for RHEL 9" type = "yum-baseurl" url = "https://cdn.redhat.com/content/dist/layered/rhel9/$(uname -m)/rhocp/4.16/os" check_gpg = true check_ssl = true system = false rhsm = true EOF
Add the update RPM source to the Image Builder by running the following command:
$ sudo composer-cli sources add rhocp-4.16.toml
Build a new image of RHEL for Edge that contains the new version of MicroShift. To determine the steps required, use the following documentation:
Update the host to use the new image of RHEL for Edge. To determine the steps required, use the following documentation:
Reboot the host to apply updates by running the following command:
$ sudo systemctl reboot
