Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1178151

Summary:	Wrong default configuration for Squid 3.3.8 on CentOS7 for Spacewalk 2.3/nightly
Product:	[Community] Spacewalk	Reporter:	Patrick Hurrelmann <redhat>
Component:	Proxy Server	Assignee:	Stephen Herr <sherr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.2	CC:	cperry
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-proxy-installer-2.3.9-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-14 19:03:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1207293

Description Patrick Hurrelmann 2015-01-02 15:08:40 UTC

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:

Comment 1 Stephen Herr 2015-02-03 21:50:03 UTC

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.

Comment 2 Grant Gainey 2015-03-23 16:59:18 UTC

Moving bugs to ON_QA as we move to release Spacewalk 2.3

Comment 3 Grant Gainey 2015-04-14 19:03:32 UTC

Spacewalk 2.3 has been released. See

https://fedorahosted.org/spacewalk/wiki/ReleaseNotes23