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.
特定のバージョンへのアップグレード

タグパラメータを指定しない場合、デフォルトで最新バージョンにアップグレードされます。特定のバージョンにアップグレードするには、タグパラメータと目的のイメージタグを指定します。

upgradeコマンドとそのパラメータの詳細については、次のコマンドを使用します。

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.