このコンテンツは選択した言語では利用できません。

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

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.

Warning

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:

Note

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

  1. Update the MicroShift RPMs by running the following command:

    $ sudo dnf update microshift
    Copy to Clipboard Toggle word wrap
  2. Restart MicroShift by running the following command:

    $ sudo systemctl restart microshift
    Copy to Clipboard Toggle word wrap
    Note

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

Warning

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:

Note

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

  1. 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)-rpms
    Copy to Clipboard Toggle word wrap
  2. For 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-rpms
    Copy to Clipboard Toggle word wrap
  3. Avoid unintended future updates into an unsupported configuration by locking your operating system version with the following command:

    $ sudo subscription-manager release --set=9.6
    Copy to Clipboard Toggle word wrap
  4. Update the MicroShift RPMs by running the following command:

    $ sudo dnf update microshift
    Copy to Clipboard Toggle word wrap
  5. Reboot the host to apply updates by running the following command:

    $ sudo systemctl reboot
    Copy to Clipboard Toggle word wrap
    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
    Copy to Clipboard Toggle word wrap
  2. Check the health check logs by running the following command:

    $ sudo journalctl -u greenboot-healthcheck
    Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2026 Red Hat
トップに戻る