Bug 832684

Summary:	Squid fails to start if named-chroot service is used
Product:	[Fedora] Fedora	Reporter:	Frank Crawford <frank>
Component:	squid	Assignee:	Michal Luscon <mluscon>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	17	CC:	frank, henrik, jonathansteffan, mluscon, paul
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-01 08:31:51 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:

Description Frank Crawford 2012-06-16 12:17:46 UTC

Description of problem:
If the named is local and started with the named-chroot service, and squid requires DNS to look up a configuration entry then may fail as the squid service on depends on named.service, not any of the other related services.

Squid can be restarted with no issues when the system is up.

Version-Release number of selected component (if applicable):
squid-3.2.0.16-1.fc17.x86_64
bind-9.9.1-2.P1.fc17.x86_64

How reproducible:
100% during booting

Steps to Reproduce:
1. Create http_port entry that requires DNS lookup, e.g FQDN.
2. Set DNS to start with named-chroot.service.
3. Reboot system.
  
Actual results:
Squid fails to start with message:
http_port: failed to resolve Host/IP: FQDN

Expected results:
Squid starts after named-chroot service has completed.

Additional info:
Simple fix is to add named-chroot.service and named-sdb-chroot.service to squid.service "After" dependency.

Comment 1 Paul Howarth 2012-07-06 14:01:17 UTC

To be safe, it probably wants:

After = nss-lookup.target

That should work for any nameserver.

https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/Systemd.special

Comment 2 Fedora Update System 2012-10-26 15:16:03 UTC

squid-3.2.3-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc18

Comment 3 Fedora Update System 2012-10-26 19:42:47 UTC

Package squid-3.2.3-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing squid-3.2.3-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16962/squid-3.2.3-2.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-11-20 13:18:51 UTC

squid-3.2.3-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc17

Comment 5 Fedora Update System 2012-11-20 15:29:08 UTC

squid-3.2.3-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc16

Comment 6 Fedora Update System 2012-11-21 04:02:23 UTC

Package squid-3.2.3-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing squid-3.2.3-2.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-18670/squid-3.2.3-2.fc17
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-12-01 08:31:53 UTC

squid-3.2.3-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2012-12-01 08:43:13 UTC

squid-3.2.3-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.