サーバのアップグレード

1. zypperを使用してソフトウェアリポジトリを更新します。

   zypper ref

2. 利用可能な更新を適用します。

   1. SLE Microの場合:

      transactional-update

      更新が適用されたら、rebootを実行して再起動します。

   2. SUSE Linux Enterprise Serverの場合:

      zypper up

3. SUSE 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

5. Check for *.rpmnew and *.rpmsave files inside the container:

   mgrctl exec 'find /etc/ -name "*.rpmnew" -o -name "*.rpmsave"'

   When an upgrade includes changes to a default configuration file that has been altered after package installation, instead of overwriting the file, one of these file types is created: *.rpmnew: contains the new default configuration and leaves your altered file untouched *.rpmsave: a copy of your altered configuration that has been replaced by the new default file

6. If you find any *.rpmnew or *.rpmsave files, examine their content and merge desirable changes.