이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 3. About updating RPMs manually


Updating Red Hat build of MicroShift for non-OSTree systems such as Red Hat Enterprise Linux (RHEL) requires updating the RPMs. For patch releases, such as 4.17.1 to 4.17.2, simply update the RPMs. For minor-version release updates, add the step of enabling the update repository 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.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.17.1 to 4.17.2.

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
  • Restart MicroShift by running the following command:

    $ sudo systemctl restart 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.

3.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.16 to 4.17.

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

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

Procedure

  1. For all lifecycles, enable the repository for your release by running the following command:

    $ sudo subscription-manager repos \
        --enable rhocp-<x.y>-for-<9>-$(uname -m)-rpms \ 1
        --enable fast-datapath-for-<9>-$(uname -m)-rpms 2
    1
    Replace <x.y> and <9> with the compatible versions of your MicroShift and Red Hat Enterprise Linux (RHEL).
    2
    Replace <9> with the compatible version of RHEL.
  2. For extended support (EUS) releases, also enable the EUS repositories by running the following command:

    `$ sudo subscription-manager repos \
        --enable rhel-<9>-for-x86_64-appstream-eus-rpms \ 1
        --enable rhel-<9>-for-x86_64-baseos-eus-rpms` 2
    1
    Replace <9> with the compatible major version number of RHEL.
    2
    Replace <9> with the compatible major version number of RHEL.
  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.4> command. 1
    1
    Replace <9.4> with the major and minor version of your compatible RHEL system.
  4. Update the MicroShift RPMs by running the following command:

    $ sudo dnf update microshift
  5. 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

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

© 2024 Red Hat, Inc.