My windows team mentioned the same issue of not being able to upgrade the
agent because of a ruby issue.. I haven't had much time yet to go jump in
and help them, but this sounds exactly like what they reported.
Bummer.. I think i'll move them to the PC1 agent and Puppet 4.2 since
they're more greenfield and see if that saves them from re-deploying just
to get to 3.8.1..
On Friday, July 17, 2015 at 8:08:52 AM UTC-5, cko wrote:
>
> By the way: ruby.exe is missing from *C:\puppet\sys\ruby\bin*
>
> Is this intended?
>
>
> On Friday, July 17, 2015 at 2:59:34 PM UTC+2, cko wrote:
>>
>> Hi all,
>>
>> updating Puppet from 3.7.5 to 3.8.1 fails on all my Windows Server 2008R2
>> nodes.
>>
>> I'm using the following code (puppet.pp):
>>
>> *package { 'Puppet':*
>> * ensure => "3.8.1",*
>> * source =>
>> "\\\\puppet\\puppetsamba\\puppet_agent\\windows\\puppet-3.8.1.msi",*
>> * provider => windows,*
>> * install_options => { 'INSTALLDIR' => 'C:\puppet' }*
>> * }*
>>
>> This completes without any problem:
>>
>> *C:\Scripts>puppet apply puppet.pp*
>> *Notice: Compiled catalog for server.local.domain in environment
>> production in 1.33 seconds*
>> *Notice: /Stage[main]/Main/Package[Puppet]/ensure: ensure changed '3.7.5'
>> to '3.8.1'*
>> *Notice: Finished catalog run in 84.66 seconds*
>>
>> But after the installation I am unable to use Puppet:
>>
>> *C:\Scripts>puppet agent -t*
>> *'ruby' is not recognized as an internal or external command, operable
>> program or batch file.*
>>
>>
>> Any ideas?
>>
>
--
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/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
