[QUOTE=jdoeconsulting;19994]Hi all,
I’ve got a crashed SUMA test server that isn’t going
to be fixed. I’ve got 2 RHEL 6 servers that are connected
to this SUMA server.
Any ideas how to unregister these 2 RHEL servers from SUMA
so I can get them connected to the normal RHN again?
Thanks[/QUOTE]
https://www.novell.com/support/kb/doc.php?id=7013242
How to unregister SUSE Manager Client
This document (7013242) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Manager
Situation
A client is registered to SUSE Manager, but needs to be unregistered.
Resolution
In order to unregister a SUSE Manager client, several rpms must be removed. Try the following method first:
zypper rm -u spacewalksd spacewalk-check zypp-plugin-spacewalk spacewalk-client-tools
This will show the following:
Refreshing service ‘spacewalk’.
Loading repository data…
Reading installed packages…
Resolving package dependencies…
The following packages are going to be REMOVED:
spacewalk-check spacewalk-client-setup spacewalksd zypp-plugin-python zypp-plugin-spacewalk
5 packages to remove.
After the operation, 301.0 KiB will be freed.
Continue? [y/n/?] (y):
The above 5 rpm packages are client specific, and should be removed.
If this fails, you’ll have to do this manually. Don’t do the “rpm -e” commands unless the “zypper rm” command above fails.
rpm -e spacewalk-client-setup
rpm -e spacewalksd
rpm -e spacewalk-check
rpm -e zypp-plugin-spacewalk
rpm -e zypp-plugin-python
After this is complete, remove the following file:
/etc/sysconfig/rhn/systemid
That file only exists on a client machine and is used to register itself with SUSE Manager.
When this is done, refresh the repositories on the server (zypper ref -s), and then list them out (zypper lr) and make sure everything looks good.
If any repositories pointing to spacewalk still exist, remove them using the following:
zypper repos -d
zypper removerepo