salt connected clients do not see latest packages in channels

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

Environment

SUSE Manager 3
SUSE Proxy 3
SUSE Manager 3.1
SUSE Proxy 3.1

Situation

Salt managed clients connected via SUSE Manager Proxy do not see the latest state of a package channel while other systems directly connected get more recent patches.

Resolution

Please compare /etc/squid/squid.conf with /usr/share/doc/proxy/conf-template/squid.conf and check if the current configuration file contains the following lines:

# salt minions get the repodata via a different URL
refresh_pattern /rhn/manager/download/.*/repodata/.*$ 0 1% 1440 ignore-no-cache reload-into-ims refresh-ims

If these are missing, please add them and restart the proxy service:

spacewalk-proxy restart

Cause

When updating from SUSE Manager 3 to 3.1 /etc/squid/squid.conf is missing the above mentioned refresh pattern as salt managed clients get their package information via a different URL than traditional managed clients (osad). This refresh pattern was introduced with SUSE Manager 3.1 and is missing when upgrading from the previous version.

This issue may also be seen while running SUSE Manager 3.

Additional Information

After upgrade to SUSE Manager Proxy 3.1, please compare the current settings in /etc/squid/squid.conf to the defaults that get deployed (/usr/share/doc/proxy/conf-template/squid.conf) when configure-proxy.sh is run for the first time to setup the proxy.

Disclaimer

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.