On Tue, Oct 23, 2012 at 7:20 AM, Ray <r...@renegade.zapto.org> wrote:
> Hi, > > I want Puppet to talk to the CloudStack API. CloudStack has many > asynchronous API calls and Puppet's catalog run tends to expire even during > simple tasks such as adding port forwarding rules: > Is it the catalog run, or the catalog retrieval that's expiring? In the example you provided the configtimeout setting affects how long the agent waits for the catalog to be compiled on the master and retrieved by the agent. Catalog runs, which is the process of applying a catalog to a system, shouldn't have a timeout by default. Hope this helps, -Jeff > root@puppet30client:~# puppet agent --test > Info: Retrieving plugin > Info: Loading facts in /var/lib/puppet/lib/facter/centos_version.rb > Info: Loading facts in /var/lib/puppet/lib/facter/network-bonds.rb > Info: Loading facts in /var/lib/puppet/lib/facter/powerstates.rb > Info: Loading facts in /var/lib/puppet/lib/facter/software_raid.rb > Info: Loading facts in /var/lib/puppet/lib/facter/centos-version.rb > > Error: Could not retrieve catalog from remote server: execution expired > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run > root@puppet30client:~# > > > When I grant the puppetrun more time than the default 2 minutes, it comes > back successfully: > > root@puppet30client:~# puppet agent --test --configtimeout 5m > Info: Retrieving plugin > Info: Loading facts in /var/lib/puppet/lib/facter/centos_version.rb > Info: Loading facts in /var/lib/puppet/lib/facter/network-bonds.rb > Info: Loading facts in /var/lib/puppet/lib/facter/powerstates.rb > Info: Loading facts in /var/lib/puppet/lib/facter/software_raid.rb > Info: Loading facts in /var/lib/puppet/lib/facter/centos-version.rb > > Info: Caching catalog for puppet30client.swisstxt.ch > Info: Applying configuration version '1351000748' > Finished catalog run in 1.88 seconds > root@puppet30client:~# > > (Don't believe the 1.88 seconds - this run took about three minutes(!)) > There's something wrong if Puppet is lying to you that much. Could you run with --evaltrace, --trace, and --debug and paste the output somewhere. A copy of the YAML report might also help diagnose the issue. Hope this helps, -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
