Description of problem: Since Network-Manager is the default network configuration demon, services should support the fact that there are no network at launch time (the network will be up seconds or minute). I'm on a big network, and DHCP requests are pretty slow (more than 1 second). That is more than the time for fedora to start Network-Manager and puppet (even if the first is S27 and the second is S98). When started with neither DNS server nor puppet-master reachable, puppetd won't be able to reach it later. Every 2 minutes, I get : Oct 30 15:59:50 b01-10 puppetd[1708]: Reopening log files Oct 30 15:59:50 b01-10 puppetd[1708]: Could not find server : getaddrinfo: Temporary failure in name resolution Oct 30 15:59:50 b01-10 puppetd[1708]: Could not request certificate: Certificate retrieval failed: Could not find server puppet this is ok since a few lines after : Oct 30 15:59:53 b01-10 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Oct 30 15:59:53 b01-10 dhclient: DHCPNAK from 10.X.Y.1 Oct 30 15:59:53 b01-10 NetworkManager: <info> DHCP: device eth0 state changed preinit -> expire Oct 30 15:59:53 b01-10 NetworkManager: <info> DHCP: device eth0 state changed expire -> preinit Oct 30 15:59:53 b01-10 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Oct 30 15:59:53 b01-10 dhclient: DHCPOFFER from 10.X.Y.8 Oct 30 15:59:53 b01-10 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Oct 30 15:59:53 b01-10 dhclient: DHCPACK from 10.X.Y.8 ... Here's network is fully working But 2 minutes later : Oct 30 16:01:50 b01-10 puppetd[1708]: Could not find server : getaddrinfo: Temporary failure in name resolution Oct 30 16:01:50 b01-10 puppetd[1708]: Could not request certificate: Certificate retrieval failed: Could not find server puppet (I checked: my DNS are ok, I can ping puppet, and other puppet clients can reach it) If I restart puppetd AFTER getting an IP and DNS conf, puppet is working again : Oct 30 15:11:21 b01-10 puppetd[3077]: Starting Puppet client version 0.24.8 and no more error every 2 mins, polling master every 30 min Version-Release number of selected component (if applicable): Name : puppet Arch : noarch Version : 0.24.8 Release : 4.fc11 Name : NetworkManager Arch : i586 Epoch : 1 Version : 0.7.1 Release : 8.git20090708.fc11 How reproducible: always Steps to Reproduce: 1. install puppet client on network-manager managed machines (for IP and DNS/resolv.conf writing) Actual results: puppet can't get their catalog Expected results: puppet client to reach puppet-master Additional info: you can start puppetd by hand, it will work : at reboot, you'll have to do it again
This is something that would need to get fixed upstream. It's not really tied to NetworkManager as much as it is puppet not recognizing when the network has changed state. Ludwin, any chance you could file a bug in the upstream tracker? (http://projects.reductivelabs.com/projects/puppet/) If not, I'll try to do so.
Oh, and if you have boxes you can test on, perhaps check if this still occurs with 0.25.1. We've not got that into the -testing repos just yet, but I have packages available at: http://tmz.fedorapeople.org/repo/puppet/ If 0.25.1 has fixed this, we don't need to bug upstream. :)
I tested the 0.25.1 packages. The error message changed to this : Oct 30 17:19:17 b01-13 puppetd[1710]: Could not request certificate: getaddrinfo: Temporary failure in name resolution But the problem is still there. I will report it at reductivelabs.
Excellent, thanks Ludwin! Feel free to add me to the watch list upstream and/or add a link to the ticket here.
Reported upstream: http://projects.reductivelabs.com/issues/2776
This is where upstart is supposed to kick in, and the puppet init script should be made compatible with upstart. Either way, there's virtually no way the old SysVinit type scripts are going to be compatible with NetworkManager (yet NetworkManagerDispatcher can help working around the issue).
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Until this is fixed upstream (which could be a while - it requires a fix to the ruby Resolv library), this is a workable fix: /etc/NetworkManager/dispatcher.d/98-puppet: #!/bin/bash # Restart puppet on network changes to pickup changes to /etc/resolv.conf # https://bugzilla.redhat.com/show_bug.cgi?id=532085 if [ -x /usr/bin/logger ]; then LOGGER="/usr/bin/logger -s -p user.notice -t NetworkManagerDispatcher" else LOGGER=echo fi if [ "$2" = "up" ] || [ "$2" = "down" ]; then $LOGGER "performing puppet condrestart" /sbin/service puppet condrestart fi systemd version would be: /bin/systemctl try-restart puppet.service
This seems even more of an issue in Fedora 17.
puppet-2.7.18-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/puppet-2.7.18-1.fc17
puppet-2.6.17-2.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/puppet-2.6.17-2.el5
puppet-2.6.17-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/puppet-2.6.17-2.el6
puppet-2.6.17-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/puppet-2.6.17-2.fc16
Package puppet-2.6.17-2.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing puppet-2.6.17-2.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6432/puppet-2.6.17-2.el6 then log in and leave karma (feedback).
puppet-2.6.17-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
puppet-2.7.18-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
puppet-2.6.17-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
puppet-2.6.17-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.