From 371b71e1d9d4df40568791bbd50004bd23e2ecba Mon Sep 17 00:00:00 2001 From: Ornela Maric Date: Tue, 22 Apr 2025 22:26:09 +0200 Subject: [PATCH] Make it more explicit to not pre-install the 5.1 server before migration. --- .../container-deployment/mlm/server-migration-mlm.adoc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/modules/installation-and-upgrade/pages/container-deployment/mlm/server-migration-mlm.adoc b/modules/installation-and-upgrade/pages/container-deployment/mlm/server-migration-mlm.adoc index 66520d11f50..4eb7bd69df7 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/mlm/server-migration-mlm.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/mlm/server-migration-mlm.adoc @@ -77,6 +77,14 @@ mgradm migrate podman --prepare ---- ==== + +[IMPORTANT] +==== +Do not pre-install {productname} on the prepared {sle-micro} {microversion} or {sles} {bci-suma} system. +The migration process is designed to perform the server installation automatically. +Running [command]``mgradm install`` and then [command]``mgradm migrate`` is not supported and will lead to an unsupported system state. +==== + .Procedure: Initial Preparation on the 4.3 Server . Stop the {productname} services: + @@ -92,8 +100,6 @@ systemctl stop postgresql === SSH Connection Preparation -Pre-installing {productname} on the prepared {sl-micro} or {sles} with [litaral]``mgradm`` is not necessary. -The migration process will take care of the server installation. .Procedure: Preparing the SSH Connection . Ensure that for [systemitem]``root`` an SSH key exists on the new {productnumber} server.