SUSE Manager/Register Clones

From MicroFocusInternationalWiki
Revision as of 13:09, 16 March 2019 by Mcalmer (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

SUSE Manager Main Page

Steps for registering a cloned system to SUSE Manager

1) Clone your system (for instance using the cloning mechanism of your favorite Hypervisor)

  • Note: Everything below is done on the cloned system, we do not manipulate the original system, and will still be registered to SUSE Manager.
  • Note: The cloned virtual machine should have a different UUID from the original (this UUID is generated by your hypervisor[*]) otherwise SUSE Manager will overwrite the original system data with the new one.

[*]Example : | VMware - Changing or keeping a UUID for a moved virtual machine (1541)If VM UUID´s are unique please | look here

2) Change hostname and ip addresses, make sure /etc/hosts has the changes you made and the right host entries.

3) Stop rhnsd daemon with
# /etc/init.d/rhnsd stop 

or # rcrhnsd stop

4) Stop osad with
# /etc/init.d/osad stop

or # rcosad stop



5.1. On the SLES 11 and RH5/6 clients exhibiting the issue enter the following as root:

 rm /var/lib/dbus/machine-id
 dbus-uuidgen --ensure

5.2. On SLES 12, or RH7-based clients exhibiting the issue enter the following as root:

 rm /etc/machine-id
 rm /var/lib/dbus/machine-id
 dbus-uuidgen --ensure
 systemd-machine-id-setup
 (Note: If using salt then also:
  service salt-minion stop
  rm -rf /var/cache/salt )

The bootstrap should now run without the duplicate key issue.



6) For traditional registered systems it is good to clean-up the systemid and osad-auth.conf file

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


The step 7) and following depends on the system OS type :

Onboarding Salt Minion Clones (SLES 11/12):

7. If your machines further have the same minion id then delete the minion_id file on each minion (FQDN will be used when it is regenerated on minion restart):

# rm /etc/salt/minion_id

8. Finally delete accepted keys from Onboarding page and system profile from SUSE Manager, and restart the minion with:

# systemctl restart salt-minion

You should be able to re-register them again, but each minion will use a different '/etc/machine-id' and should now be correctly displayed on the System Overview page.

Next step for SLES 12 :

6)
    # rm  -f /etc/zypp/credentials.d/{SCCcredentials,NCCcredentials}

7) re-run the bootstrap script

8) you should now see the cloned system in SUSE Manager without overwriting the system it was cloned from.

Next step for SLES 11 :

6)
# suse_register -E 

( --erase-local-regdata, Erase all local files created from a previous executed registration. This option make the system look like never registered)


7) re-run the bootstrap script

8) you should now see the cloned system in SUSE Manager without overwriting the system it was cloned from.

Next step for SLES 10 :

6)
# rm -rf /etc/{zmd,zypp}
7)
# rm -rf /var/lib/zypp/ ¡¡¡¡¡ except /var/lib/zypp/db/products/ !!!!!
8)
# rm -rf /var/lib/zmd/

9) re-run the bootstrap script

10) you should now see the cloned system in SUSE Manager without overwriting the system it was cloned from.

Next step for RHEL 5 & 6 & 7:

6)
# rm  -f /etc/NCCcredentials 

7) re-run the bootstrap script

8) you should now see the cloned system in SUSE Manager without overwriting the system it was cloned from.