Hi folks, I am building a server using Gentoo Linux and was about to start automating the package loads using puppet. First things first I loaded the latest and greatest facter and puppet from gems. Got the new SSL certificate loaded and ran puppetd --test and expected to see a base manifest loaded. Instead here is how it went: puppetd --test err: Could not retrieve catalog from remote server: Error 400 on SERVER: No support for http method POST warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Eh? Never saw that before... -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I ran into this as well. Figuring it had something to do with version inconsistency, I upgraded my master to 2.7.1 (which is the latest and greatest that my client ended up with) and it seemed to resolve the problem. Note that it DID introduce other unexpected behavior for me, so I might revert the master and all clients back to an older version for the time being. YMMV. On Jun 22, 11:19 am, Peter Berghold <salty.cowd...@gmail.com> wrote:> Hi folks, > > I am building a server using Gentoo Linux and was about to start automating > the package loads using puppet. First things first I loaded the latest and > greatest facter and puppet from gems. Got the new SSL certificate loaded > and ran puppetd --test and expected to see a base manifest loaded. > > Instead here is how it went: > > puppetd --test > err: Could not retrieve catalog from remote server: Error 400 on SERVER: No > support for http method POST > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > Eh? Never saw that before... > > -- > Peter L. Berghold > Owner, Shark River Technical Solutions LLC-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Jun 27, 2011 at 14:10, Arthur Nisnevich <arthur@crowdspoke.com> wrote:> > I ran into this as well. Figuring it had something to do with version > inconsistency, I upgraded my master to 2.7.1 (which is the latest and > greatest that my client ended up with) and it seemed to resolve the > problem.It would. Specifically, we support a *newer* master than clients, but not the other way around. (It might, occasionally, work, but we make no promises in that direction.) So, if you have 2.7 clients you need a 2.7 master.> Note that it DID introduce other unexpected behavior for me, so I > might revert the master and all clients back to an older version for > the time being. YMMV.I trust you filed bugs about those, so we can fix ''em. ;) daniel> > On Jun 22, 11:19 am, Peter Berghold <salty.cowd...@gmail.com> wrote: >> Hi folks, >> >> I am building a server using Gentoo Linux and was about to start automating >> the package loads using puppet. First things first I loaded the latest and >> greatest facter and puppet from gems. Got the new SSL certificate loaded >> and ran puppetd --test and expected to see a base manifest loaded. >> >> Instead here is how it went: >> >> puppetd --test >> err: Could not retrieve catalog from remote server: Error 400 on SERVER: No >> support for http method POST >> warning: Not using cache on failed catalog >> err: Could not retrieve catalog; skipping run >> >> Eh? Never saw that before... >> >> -- >> Peter L. Berghold >> Owner, Shark River Technical Solutions LLC > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <daniel@puppetlabs.com> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Jun 22, 2011 at 10:19 AM, Peter Berghold <salty.cowdawg@gmail.com>wrote:> > err: Could not retrieve catalog from remote server: Error 400 on SERVER: No > support for http method POST >To explain this error a bit more, we''ve moved the catalog retrieval to a POST rather than a GET to avoid the compile-time size limitations on fact data that we had with GET. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.