Issue #4450 has been updated by Luke Kanies. Status changed from Needs design decision to Accepted Assigned to deleted (Luke Kanies)
---------------------------------------- Feature #4450: client should retry if connection to master fails http://projects.puppetlabs.com/issues/4450 Author: Alan Barrett Status: Accepted Priority: Normal Assigned to: Category: plumbing Target version: Affected version: Keywords: Branch: It would be nice if the client retried several times over say a 30-second period when it can't connect to the master. Use case 1: Restart the puppetmaster while a client is busy processing a catalog. At present, the client will fail to fetch any files with puppet:/// source URLs, leading to many error messages on the client. Use case 2: Run puppetmasterd and a puppetd client on the same host. Have a manifest with "notify => Service[puppetmasterd]" after upgrading the package that contains puppet itself, or upgrading ruby, or some other dependency. The client will upgrade the puppet package, and restart puppetmasterd. Then the client will try to send a report to the master, and fail, like this: <pre> notice: Package[puppet]/ensure: ensure changed '0.25.5,REV=2010.06.17.13.13' to '0.25.5,REV=2010.08.03.09.06' info: Package[puppet]: Scheduling refresh of Service[puppetmasterd] notice: Service[puppetmasterd]: Triggering 'refresh' from 1 dependencies err: Reporting failed: Connection refused - connect(2) notice: Finished catalog run in 202.94 seconds </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
