How to unregister a SUSE Manager Client
This document (7013242) is provided subject to the disclaimer at the end of this document.
SUSE Manager 4 Server
SUSE Manager 3.2 Server
First of all, the osad client should be stopped on the system (in case it is being used, SLES 15 doesn't use it):
systemctl stop osad
zypper rm -u spacewalksd spacewalk-check zypp-plugin-spacewalk spacewalk-client-tools osad python2-zypp-plugin-spacewalk python2-spacewalk-check python2-spacewalk-client-setup
Refreshing service 'spacewalk'.
Resolving package dependencies...
The following packages are going to be REMOVED:
spacewalk-check spacewalk-client-setup spacewalksd zypp
5 packages to remove.
After the operation, 301.0 KiB will be freed.
Continue? [y/n/?] (y):
If this fails, they should be manually removed. The commands "rpm -e" should not be used unless the "zypper rm" command above failed.
rpm -e spacewalk-client-setup spacewalksd spacewalk-check zypp-plugin-spacewalk osad python2-zypp-plugin-spacewalk python2-spacewalk-check python2-spacewalk-client-setup
On SLES 15 client remove below packages if installed:
rpm -e spacewalk-client-setup mgr-daemon spacewalk-check zypp-plugin-spacewalk mgr-osad python3-zypp-plugin-spacewalk python3-spacewalk-check python3-spacewalk-client-setup
After this is complete, the following file should be removed: /etc/sysconfig/rhn/systemid.
If any repositories pointing to spacewalk still exist, remove them using the following:
zypper repos -d
zypper removerepo <ID of the repo in the output from previous command>
systemctl stop salt-minion
rpm -e salt salt-minion python2-salt
SLES 15 clients use python3-salt instead of python2-salt:
rpm -e salt salt-minion python3-salt
SUSE Manager Server:
Now the system can be removed from the inventory using the SUMA Server WebUI, or from command line using spacecmd:
spacecmd system_delete FQDN
salt-key -d FQDN
For very specific cases, the registration might still not be possible after having unregistered the minion. As a last result, a couple of salt files should be deleted in the master before trying to register again:
The following error is an indication that the file exists and impedes registration and migration of the client.
Can't get available migrations from server: SUSE::Connect::ApiError: The requested products 'SUSE Manager Client Tools for SLE 15 x86_64' are not activated on the system.
'/usr/lib/zypper/commands/zypper-migration' exited with status 1
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:7013242
- Creation Date: 10-Sep-2013
- Modified Date:11-Apr-2022
- SUSE Manager
For questions or concerns with the SUSE Knowledgebase please contact: firstname.lastname@example.org