Thanks,  I have tested it on my puppet 3.0 rc-5 master is working great 
now.  

On Tuesday, September 4, 2012 3:44:10 AM UTC-5, Erik Dalén wrote:
>
> I've released a new version now that contains a fix for this, thanks 
> for the report. 
>
> On 1 September 2012 11:03, Erik Dalén <erik.gus...@gmail.com <javascript:>> 
> wrote: 
> > I'll try to take a look at this during the weekend and see if I can 
> > create something that is compatible with both puppet 2.7 and 3.0. Can 
> > probably try to make the requests more like the puppetdb-terminus does 
> > them as it works on both. 
> > 
> > On 31 August 2012 18:28, Chris Price <ch...@puppetlabs.com <javascript:>> 
> wrote: 
> >> Chuck, 
> >> 
> >> The cause of this issues is that we introduced our own HTTP connection 
> >> wrapper in 3.0 (rather than using Net::HTTP directly).  This allows us 
> to do 
> >> a better job of centralizing the logic related to managing SSL setup 
> and 
> >> error handling. 
> >> 
> >> Our Connection class provides a subset of the methods available on 
> Ruby's 
> >> HTTP class, and it looks like puppetdbquery is using one of the methods 
> that 
> >> don't currently exist in our new API. 
> >> 
> >> The possible solutions would be to add the missing #start method to our 
> new 
> >> class, or to tweak puppetdbquery so that it doesn't rely on the #start 
> >> method.  I'll ping the folks on our platform team and see what their 
> >> thoughts are. 
> >> 
> >> Thanks for the heads up! 
> >> Chris 
> >> 
> >> 
> >> On Thursday, August 30, 2012 6:04:27 AM UTC-7, Chuck wrote: 
> >>> 
> >>> I have puppetdbquery working on my puppet-2.7.16 puppet master but I 
> am 
> >>> getting an error when using it with puppet-3.0.0-rc5 
> >>> 
> >>> https://github.com/dalen/puppet-puppetdbquery 
> >>> 
> >>> This is the error I am getting: 
> >>> 
> >>>   err: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: 
> >>> undefined method `start' for 
> >>> #<Puppet::Network::HTTP::Connection:0x7fa6e25db7c8> 
> >>> 
> >>> How would I go about finding the actual cause of this issue? 
> >>> 
> >>> 
> >>> Thanks, 
> >> 
> >> -- 
> >> You received this message because you are subscribed to the Google 
> Groups 
> >> "Puppet Users" group. 
> >> To view this discussion on the web visit 
> >> https://groups.google.com/d/msg/puppet-users/-/cnmWN3qKeJYJ. 
> >> 
> >> To post to this group, send email to 
> >> puppet...@googlegroups.com<javascript:>. 
>
> >> To unsubscribe from this group, send email to 
> >> puppet-users...@googlegroups.com <javascript:>. 
> >> For more options, visit this group at 
> >> http://groups.google.com/group/puppet-users?hl=en. 
> > 
> > 
> > 
> > -- 
> > Erik Dalén 
>
>
>
> -- 
> Erik Dalén 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/pDzfpt-YRTEJ.
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.

Reply via email to