Description of problem: Spacewalk-Proxy setup deploys a default configuration on CentOS7 for Squid which does not work with squid 3.3.8. Version-Release number of selected component (if applicable): Spacewalk Proxy 2.3/nightly with Squid 3.3.8 How reproducible: always Steps to Reproduce: 1. Install Spacewalk Proxy 2.3/nightly on CentOS7 2. Start Squid Actual results: Squid fails to start and logs the following error: aclParseAclList: ACL name 'KB' not found. Bungled /etc/squid/squid.conf line 54: range_offset_limit -1 KB FATAL: Bungled /etc/squid/squid.conf line 54: range_offset_limit -1 KB Squid Cache (Version 3.3.8): Terminated abnormally. Expected results: Squid starts successfully Additional info:
This is because of squid changing behavior between 3.1 and 3.2. See: http://www.squid-cache.org/Versions/v3/3.1/cfgman/range_offset_limit.html http://www.squid-cache.org/Versions/v3/3.2/cfgman/range_offset_limit.html The fix is to change the "-1 KB" value to "none". Committing to Spacewalk master: 6cf5c0900b85ce011d7cc395e9721b062320f9bb There also appear to be other problems on RHEL 7 related to selinux and something else that I haven't figured out yet. I'll continue investigating tomorrow.
Moving bugs to ON_QA as we move to release Spacewalk 2.3
Spacewalk 2.3 has been released. See https://fedorahosted.org/spacewalk/wiki/ReleaseNotes23