SUSE Multi-Linux Manager 서버 업그레이드

Before running the upgrade command, it is required to update the host operating system. Updating the host operating system will also result in the update of the SUSE Multi-Linux Manager tooling such as the mgradm tool.

절차: 서버 업그레이드

  1. Refresh software repositories with zypper:

    zypper ref

  2. 호스트 운영 체제에 따라 다음 단계를 진행합니다.

    SL Micro 같은 트랜잭션 시스템의 경우:

    1. Apply available updates with transactional-update:

      transactional-update

    2. If updates were applied, reboot.

    SUSE Linux Enterprise Server의 경우:

    Update installed software with zypper:

    zypper up

  3. 다음 명령을 사용하여 SUSE Multi-Linux Manager 서버 컨테이너를 업데이트할 수 있습니다.

    Risk of Automated Version Downgrade and PTF Loss

    Running the mgradm upgrade podman command when no newer upgrade is available will cause the system to automatically revert to the base version. This process removes all currently applied Program Temporary Fixes (PTFs) without a confirmation prompt.

    To avoid unintended data or fix loss, verify upgrade availability before execution. Future releases will include a confirmation prompt to prevent this behavior.

    		 
    mgradm upgrade podman

    이 명령은 컨테이너의 상태를 최신 상태로 가져오고 서버를 다시 시작합니다.

  4. 사용하지 않는 컨테이너 이미지를 정리하여 디스크 공간을 확보합니다.

    podman image prune -a

    In some upgrades, multiple *.rpmnew and *.rpmsave files may be generated. The presence or number of these files does not indicate that manual action is required. In SUSE Multi-Linux Manager container environments, required configuration changes are applied automatically during the upgrade process. These files are created as a result of differences between packaged defaults and existing configuration files, and may also include internal or informational changes that are not intended to be merged. If manual action is required for a configuration change, it will be explicitly documented in the release notes or upgrade documentation.

    Do not treat these files as a post-upgrade checklist or merge them in bulk. Only review a file if you are actively troubleshooting a specific issue and understand the impact of the configuration it contains. If a change is required, it should be applied intentionally based on a known requirement, not by copying differences from these files. If you are unsure, leave the file unchanged.
타사 SSL 인증서로 업그레이드

In previous versions, the database container needed to have an SSL certificate with the following Subject Alternate Names (SANs):

  • db

  • reportdb

This is no longer required. The database container needs only the externally facing fully qualified domain name. The old certificates with db and reportdb SANs can be still used.

The same certificate can be used for both the main container and the database one.

In order to pass the new certificates to the upgrade command, use the --ssl-db-ca-root, --ssl-db-cert and --ssl-db-key parameters.
특정 버전으로 업그레이드

태그 파라미터를 지정하지 않으면 기본적으로 가장 최신 버전으로 업그레이드됩니다. 특정 버전으로 업그레이드하려면 태그 파라미터에 원하는 이미지 태그를 지정합니다.

업그레이드 명령과 해당 파라미터에 대한 자세한 내용은 다음 명령을 참조하십시오.

Risk of Automated Version Downgrade and PTF Loss

Running the mgradm upgrade podman command when no newer upgrade is available will cause the system to automatically revert to the base version. This process removes all currently applied Program Temporary Fixes (PTFs) without a confirmation prompt.

To avoid unintended data or fix loss, verify upgrade availability before execution. Future releases will include a confirmation prompt to prevent this behavior.

 
mgradm upgrade podman -h

For air-gapped installations, first upgrade the container RPM packages, then run the mgradm command.

1. 데이터베이스 백업 볼륨

Server migration or upgrade with mgradm migration or mgradm upgrade can create a volume with the database backup.

When the PostgreSQL database version is increased, the old database must be stored in a separate location before running the upgrade. For this purpose mgradm dynamically creates the volume var-pgsql-backup. When the migration or upgrade is done and the user has validated that the new system is working as expected, this volume can be removed safely.