That ticket looks like the issue I'm having!

I look forward to the upcoming releases so we can start working on a plan 
to upgrade.  If the new puppetserver would talk nicely to older puppet's, 
that would be great.  It's going to suck when we have to bring up systems 
that have been offline and have older versions of puppet that need to be 
upgraded.

On Friday, April 17, 2015 at 4:25:59 PM UTC-7, Kylo Ginsberg wrote:
>
> On Fri, Apr 17, 2015 at 3:12 PM, Ken Bowley <kbo...@gmail.com 
> <javascript:>> wrote:
>
>> Puppet 4 needs a lot of new directories in order to even attempt to run.  
>> It would be nice if puppet had a way to create the directory structure that 
>> it needs in order to run.
>>
>
> Hi Ken,
>
> I've just filed https://tickets.puppetlabs.com/browse/PUP-4436, which I 
> think is the issue you're seeing. If that doesn't describe the problem, 
> let's dig in some more.
>  
>
>>
>> For now I'm trying to ignore the seemingly non-existent upgrade path from 
>> puppet 3 to puppet 4 that doesn't involve firing up a new puppet 4 server 
>> to run alongside the puppet 3 server.
>>
>
> Yep, that's the only upgrade path at the moment but upcoming releases aim 
> to make the 3 -> 4 upgrade smoother. Stay tuned!
>
> Thanks,
> Kylo
>  
>
>>
>> On Friday, April 17, 2015 at 3:04:51 PM UTC-7, Tim Skirvin wrote:
>>>
>>> Ken Bowley <kbo...@gmail.com> writes: 
>>>
>>> > We've been using Puppet since the 0.24 days, and it's always been 
>>> fairly 
>>> > simple to add in a new system. 
>>>
>>> > Do a base install (Linux or Mac OS X) 
>>> > Install Ruby if Linux 
>>> > gem install puppet 
>>> > run puppet 
>>> > sign the cert on the puppetmaster 
>>> > let puppet take care of everything else. 
>>>
>>> [...] 
>>>
>>> > This workflow no longer works with Puppet 4. 
>>>
>>>         I haven't investigated any of this yet; what doesn't work? 
>>>
>>>                                     - Tim Skirvin (tski...@fnal.gov) 
>>> -- 
>>> HPC Systems Administrator / Developer    
>>> http://www.linkedin.com/in/tskirvin 
>>>   Fermilab - USCMS-T1 Collaboration        Experiment Computing 
>>> Facilities 
>>>
>>  -- 
>> 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...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/bd5ade5e-169f-4d30-be91-b3fc6152bff9%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/puppet-users/bd5ade5e-169f-4d30-be91-b3fc6152bff9%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Kylo Ginsberg | ky...@puppetlabs.com <javascript:> | irc: kylo | twitter: 
> @kylog
>
> *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, 
> Oregon! Join us October 5-9.*
> *Register now to take advantage of the Early Adopter discount 
> <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter>
>  *
> *—**save $349!*
>  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a2a509d1-bab0-48e3-92ab-7bd4990ba89b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to