Bug 750550

Summary: Squid might depend on named
Product: [Fedora] Fedora Reporter: Göran Uddeborg <goeran>
Component: squidAssignee: Jiri Skala <jskala>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: aglotov, henrik, jonathansteffan, jskala
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: squid-3.2.0.13-4.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 22:24:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Göran Uddeborg 2011-11-01 14:55:16 UTC 
Description of problem:
A squid configuration file can contain names that needs name resolution.  If squid and the DNS server runs on the same host, the DNS server needs to be started first.  But there is nothing enforcing this.  Which makes 

Version-Release number of selected component (if applicable):
squid-3.2.0.12-1.fc16.x86_64

How reproducible:
It happened every time for me, though since it is a timing issue, I guess you could have luck and get it right occasionally.

Steps to Reproduce:
1. Configure squid to listen to a port using a name that is defined in DNS
2. Reboot
  
Actual results:
Squid fails with an error message like  this:
  squid[1391]: 2011/10/06 22:46:53| http(s)_port: failed to resolve Host/IP: mimmi.uddeborg

Expected results:
Squid should come up normally.

Additional info:
I've avoided the problem locally by adding "named.service" to the "After" line in /lib/systemd/system/squid.service.  But since that file isn't marked as a %config, this solution will not be persistent.  When I upgrade squid, I will have to (remember to) redo it.
Comment 1 Jiri Skala 2011-11-03 14:10:32 UTC 
I've extended 'After' of squid.service in rawhide. Could you verify it? I'd backport it to F16 later.
Comment 2 Göran Uddeborg 2011-11-03 21:57:59 UTC 
You refer to 3.2.0.13-4.fc17, right?  I downloaded it from Koji and installed on my (otherwise mostly F16) system.  Things comes up in the right order when I reboot.

So yes, it works just fine for me.
Comment 3 Fedora Update System 2011-11-04 07:57:51 UTC 
squid-3.2.0.13-4.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/FEDORA-2011-14951
Comment 4 Fedora Update System 2011-11-04 21:49:25 UTC 
Package squid-3.2.0.13-4.fc16:
* should fix your issue,
* was pushed to the Fedora 16 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.0.13-4.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-14951
then log in and leave karma (feedback).
Comment 5 Fedora Update System 2011-11-14 22:24:25 UTC 
squid-3.2.0.13-4.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.