SUSE Support

Here When You Need Us

SUSE Manager Proxy disappeared from SUSE Manager

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


SUSE Manager 4.1 Server
SUSE Manager 4.1 Proxy


A registered SUSE Manager Proxy disappeared from SUSE Manager Server. The proxy was not visible within the System Overview list in the WebUI but still visible within the Salt keys. When the salt-minion service was restarted on the proxy, the system appeared again in the SUSE Manager overview list, however, it lost its proxy role and it was visible as regular client/minion only. When the proxy was reconfigured using the proxy setup guide ( was used with the answer file used for the initial proxy setup), the proxy role was recovered, however, no clients were visible behind that proxy.


There were 2 possible approaches how to restore clients:
  1. remove them from SUSE Manager and bootstrap them again (which would mean loosing all its event history, formula configurations, group assignments etc.)
  2. Re-activate them using re-activation key
Engineering provided a script "" which can be used to restore invisible clients behind the affected proxy. The script:
  1. identifies which clients are supposed to be register via the affected proxy (based on proxy FQDN)
  2. creates re-activation key for all affected clients
  3. adds the re-activation key into "/etc/salt/minion.d/susemanager.conf"
  4. restarts salt-minion service on affected clients

All clients were properly visible behind Proxy once they were re-activated using the mentioned script.
The script was made available as a pull request to the uyuni-project.


It is not clear why the Proxy vanished from SUSE Manager. There is a chance that it was removed by accident, however, there are no logs which would prove that. During the night when the issue happened, there was a time shift on the affected Proxy - time was moved back to Jan-19-2021. However, there is no data which would confirm that this caused the issue.

Additional Information

Interesting is that the clients were still communicating via the Proxy, they were just not visible/shown behind the Proxy in the WebUI. It was tested using the following approach:

1. Run the following command on SUSE Manager:
  salt client_name grains.item master (on SUSE Manager)

2. Stop the salt-broker on SUSE Manager Proxy:
    systemctl stop salt-broker

3. run the salt command from 1. again, it will hang

4. As soon the salt-broker on the SUSE Manager Proxy is restarted (systemctl start salt-broker), a reply from salt was received immediately. 


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:000020281
  • Creation Date: 11-Jun-2021
  • Modified Date:16-Jun-2021
    • SUSE Manager Server
    • SUSE Manager
    • SUSE Manager Proxy

< Back to Support Search

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

SUSE Support Forums

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

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.

Open an Incident

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