SUSE Support

Here When You Need Us

Changing the Base OS for SUSE Multi Linux Manager 5

This document (000021804) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 5.0
SUSE Multi Linux Manager 5.0
SUSE Linux Enterprise Micro 5.5
SUSE Linux Enterprise Server 15 SP6


Situation

Customers who initially configured SUMA5/SMLM5 on SLEM container hosts may wish to move the container on to a SLES container host, and thus the persistent storage data store (/var/lib/containers/storage/volumes/) from the SMLM5 instance running on a SLEM container host must be somehow moved to the instance running on a SLES15SP6 container host.

Resolution

Example 1, useful in Hypervisor scenarios...
1. Assuming all channel sync is complete, shut down the SUMA5/SMLM5 container:
# mgradm stop.
2. In the Hypervisor, detach the disk storage devices from the SLEM container host VM and present them to the SLES container host VM.
3. Install and configure SLES, ensuring the <fqdn> and IP match that of the original SLEM container host.
4. Copy the persistent storage entries from the SLEM container host /etc/fstab to the SLES container host /etc/fstab, for example:
UUID=91ca0129-315b-4776-bb59-51c27833ff25 /var/lib/containers/storage/volumes xfs defaults,nofail 1 2
5. Deploy SUMA5/SMLM5 on SLES15SP6 as per the official SUSE documentation.  The installer will automatically detect and configure the persistent storage accordingly.


Example 2, useful for limited disk space/server instance scenarios...
1. Assuming all channel sync activity is complete, shut down the SUMA5/SMLM5 container:
# mgradm stop
2. Copy the contents of the persistent storage devices from the SLEM container host to a temporary storage location, for example:
# rsync -Pav /var/lib/containers/storage/volumes/ <<temp_mount_point>>
3. Shut down the SUMA5/SMLM5 system:
# mgradm stop && shutdown -P
4. Install and configure SLES the official SUSE documentation, ensuring the <fqdn> and IP are the same as that of the original SLEM container host.
5. Deploy SUMA5 on SLES as per the official SUSE documentation.
6. Shut down the SUMA container:
# mgradm stop
7. Copy the contents of the <<temp_mount_point>> to the SLES container host:
# rsync -Pav /var/lib/containers/storage/volumes/ root@<sles-fqdn>:/var/lib/containers/storage/volumes
8. Start SUMA5/SMLM5 on SLES:
# mgradm start
SUMA5/SMLM5 will automatically use the persistent storage accordingly.

Additional Information

Please note that while a subscription of SLE Micro 5.5 is included with SUMA5/SMLM5, however, to run SUMA5/SMLM5 on SLES15SP6, a separate subscription is required.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000021804
  • Creation Date: 22-Apr-2025
  • Modified Date:28-Apr-2025
    • SUSE Linux Enterprise Server
    • SUSE Manager Server
    • SUSE Manager
    • SUSE Linux Enterprise Micro

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

tick icon

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

tick icon

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

tick icon

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.