Unfortunately no. It uses cached catalog only if puppet master returns error code. If it is completely unavaliable agent just does nothing. Logs contain something like >>> 2013-02-13T18:02:09.416421+04:00 distbuilder-b puppet-agent[1432]: Puppet --listen / kick is deprecated. See http://links.puppetlabs.com/puppet-kick-deprecation 2013-02-13T18:02:09.703607+04:00 distbuilder-b puppet-agent[1432]: Starting Puppet client version 3.0.1 2013-02-13T18:02:09.704367+04:00 distbuilder-b puppet-agent[1432]: Reopening log files 2013-02-13T18:02:09.820540+04:00 distbuilder-b puppet-agent[1432]: Reopening log files 2013-02-13T18:02:09.861180+04:00 distbuilder-b puppet-agent[1432]: Failed to apply catalog: getaddrinfo: Name or service not known 2013-02-13T18:02:09.879258+04:00 distbuilder-b puppet-agent[1432]: Could not send report: getaddrinfo: Name or service not known <<<
вторник, 12 февраля 2013 г., 19:23:00 UTC+4 пользователь Paul Tötterman написал: > > Hi Ivan, > > >> Had somebody invented something like that and how? >> > > Doesn't puppet do that right now? If it's unable to fetch a new catalog > from master it uses the cached catalog that it has received previously. > > Cheers, > Paul > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
