stopping server before reboot for migration from 5.0 (#4233)

https://bugzilla.suse.com/show_bug.cgi?id=1247705
SUSE/spacewalk#28033

plus drive-by edits

Author: keichwa

CHANGELOG.md

@@ -1,3 +1,6 @@
+- Documented stopping the server before rebooting the host operating
+  system for the migration from 5.0 to 5.1 in Installation and
+  Upgrade Guide (bsc#1247705)
 - Removed reference to smdba from reference Guide (bsc#1247213)
 - Fixed procedure name for confidential computing in Administration
   Guide (bsc#1247318)

modules/installation-and-upgrade/pages/container-deployment/mlm/migrations/proxy/proxy-mlm-50-51.adoc

@@ -373,7 +373,6 @@ Ensure all relevant proxy containers are up:
 - `proxy-tftpd`
 - `proxy-ssh`
 
-_____
 
 
 === Migration Complete

modules/installation-and-upgrade/pages/container-deployment/mlm/migrations/server/server-mlm-50-51.adoc

@@ -6,7 +6,7 @@
 [NOTE]
 ====
 * {productname} 5.0 must be stopped before upgrade.
-* {productname} 5.0 is not supported on top of {sl-micro} 6.1 & {sles} 15 SP7 as host os
+* {productname} 5.0 is not supported on top of {sl-micro} 6.1 & {sles} 15 SP7 as host OS.
 ====
 
 include::../../../snippet-hardened-tmpdir.adoc[leveloffset=+2]
@@ -39,14 +39,14 @@ SUSEConnect --status-text
 
 +
 
-**Confirm:**
+Confirm:
 
 - Base OS: `SUSE Linux Enterprise Micro 5.5`
 - Extension: `SUSE Manager Server 5.0 Extension`
 
 +
 
-. Ensure System is Updated
+. Ensure system is updated
 
 +
 
@@ -57,19 +57,25 @@ transactional-update patch
 
 +
 
+--
 
-* If patches were applied, **reboot the system** before proceeding to migration:
+* If patches were applied, stop the server and then reboot the system before proceeding to migration:
+
++
 
 [source,console]
 ----
+mgradm stop
 reboot
 ----
 
 * If no updates were found, you can proceed directly to the migration step.
 
+--
+
 +
 
-. Start the Migration:
+. Start the migration:
 
 +
 
@@ -84,18 +90,19 @@ Follow the prompts and select the available migration to **SUSE Linux Micro 6.1*
 
 +
 
-. Reboot to Apply Changes
+. Stop the server and then reboot to apply changes:
 
 +
 
 [source,console]
 ----
+mgradm stop
 reboot
 ----
 
 +
 
-. Post-Reboot Checks:
+. Post-Reboot checks:
 
 +
 
@@ -143,7 +150,7 @@ systemctl restart sshd
 
 For more information, see xref:administration:troubleshooting/tshoot-remote-root-on-micro.adoc[].
 
-. Upgrade Server Containers
+. Upgrade server containers
 
 +
 
@@ -229,7 +236,7 @@ This document provides the tested procedure to upgrade a SUSE Linux Enterprise S
 [role=procedure]
 _____
 
-. Verify Current Product Status
+. Verify current product status
 
 +
 
@@ -240,7 +247,7 @@ SUSEConnect --status-text
 
 +
 
-**Confirm:**
+Confirm:
 
 +
 
@@ -249,7 +256,7 @@ SUSEConnect --status-text
 
 +
 
-. Apply All System Patches
+. Apply all system patches
 
 +
 
@@ -260,12 +267,13 @@ zypper patch
 
 +
 
-*Reboot* if the update stack was updated:
+. Stop the server, and then reboot if the update stack was updated:
 
 +
 
 [source,console]
 ----
+mgradm stop
 reboot
 ----
 
@@ -286,18 +294,19 @@ Zypper will show the possible migration targets with detailed summaries.
 
 . Select the appropriate target, and follow the prompts to complete the migration.
 
-. After the upgrade completes, reboot the system:
+. After the upgrade completes, stop the server and then reboot the system:
 
 +
 
 [source,console]
 ----
+mgradm stop
 reboot
 ----
 
 +
 
-. Post-Reboot: Verify Upgrade Status
+. Post-Reboot: Verify upgrade status
 
 +
 
@@ -316,7 +325,7 @@ Expected output:
 
 +
 
-. Upgrade Server Containers
+. Upgrade server containers
 
 +
 
@@ -331,7 +340,7 @@ Follow prompts to pull the new container images and reconfigure the environment.
 
 +
 
-. Check Running Containers
+. Check running containers
 
 +
 
@@ -349,7 +358,7 @@ Expected containers:
 
 +
 
-. Verify {productname} Tools Version
+. Verify {productname} Tools version
 
 +