Short tip: Manage cloned systems with SUSE Manager

calendar May 22, 2018 · 1 min read · salt kurztipp  ·
Share on: linkedin copy

It is a common procedure to use templates ("golden images") when deploying virtual machines. Recently I had an issue when deploying SLES machines - newly registered systems within SUSE Manager replaced older one. The management agent was installed within the template.

For classic systems (registered via RHNSD and OSAD) it is sufficient to remove the following files:

1# rm /etc/sysconfig/rhn/{osad-auth.conf,systemid}

On Salt systems, the following file needs to be removed:

1# rm /etc/salt/minion_id

In my case, this step was not sufficient as an unique installation number is generated during the installation. This number is used when the system is registered within SUSE Manage - so ensure to re-create this identifier:

1# cat /etc/machine-id ; rm /etc/machine-id
21b2380c0a275609d1ce8144a5ad49b86
3
4# systemd-machine-id-setup
5# cat /etc/machine-id
65c1815d1c162814a2df2568b7de25a73

On SLES 11 systems, this file does not exist. Use the following two commands:

1# rm /var/lib/dbus/machine-id
2# dbus-uuidgen --ensure

Afterwards, registering new machines worked like a charm again.

Translations: