Chapter 4. About updating MicroShift RPMs manually


Updating MicroShift for non-OSTree systems such as Red Hat Enterprise Linux (RHEL) requires downloading then updating the RPMs. For patch releases, such as 4.15.1 to 4.15.2, download and update the RPMs. For minor-version release updates, add the step of enabling the update repository using your subscription manager.

Important

MicroShift updates are supported from one minor version to the next in sequence. For example, you must update 4.14 to 4.15.

For either upgrading with patch updates or a minor-version update, you can back up application data as needed and move the data copy to a secure location.

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. A system reboot is not required for patch updates. For example, use the following procedure to upgrade from 4.14.0 to 4.14.1.

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.
Note

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
Note

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.

4.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.14 to 4.15.

Important

You can only update MicroShift from one version to the next in sequence. Jumping minor versions is not supported. For example, must update 4.14 to 4.15.

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.
Note

You cannot downgrade MicroShift with this process. Downgrades are not supported.

Procedure

  1. Enable the MicroShift repositories by running the following command:

    $ sudo subscription-manager repos \
        --enable rhocp-4.15-for-rhel-9-$(uname -m)-rpms \
        --enable fast-datapath-for-rhel-9-$(uname -m)-rpms
  2. Update the MicroShift RPMs by running the following command:

    $ sudo dnf update microshift
  3. Reboot the host to apply updates by running the following command:

    $ sudo systemctl reboot
Note

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

  1. Check if the health checks exited with a successful boot by running the following command:

    $ sudo systemctl status greenboot-healthcheck
  2. Check the health check logs by running the following command:

    $ sudo journalctl -u greenboot-healthcheck

Additional resources

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.