[Puppet Users] Cannot update Puppet 3.7.5 to 3.8.1 on Windows

Cko

at Jul 17, 2015 at 1:09 pm

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 [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3a193a17-5ee3-4468-a15e-3edaa823a266%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

reply | permalink

Byron Miller

at Jul 17, 2015 at 1:34 pm

⇧

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 [email protected].
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.

reply | permalink

Dhaval thakar

at Jul 17, 2015 at 4:37 pm

⇧

I am facing same issue with 3.7.5 to 3.8.1 upgrade.

On 17-Jul-2015 7:04 pm, "Byron Miller" wrote:

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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

--
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 [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAAzj036d%2BMDJ7FY1tY8d60yiD327MeMUySku4%2BVrpmZdmSMjbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

reply | permalink

Rob Reynolds

at Jul 17, 2015 at 9:38 pm

⇧

On Fri, Jul 17, 2015 at 8:34 AM, Byron Miller wrote:

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?

This is most assuredly not intended. I can say that we don't really support
using puppet to upgrade puppet - because file locking on Windows. It
appears you have run into this. We have an upcoming epic for this in
MODULES-2040[1], which will be similar to how Puppetlabs-Puppet_Agent will
handle upgrades for WIndows agents[2][3].

I would highly suggest that you follow suit on those ideas until something
is in place or upgrade out of band e.g. use something besides Puppet to
upgrade Puppet on Windows. You can also try using the puppetversion
module[4].

[1] https://tickets.puppetlabs.com/browse/MODULES-2040
[2]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/manifests/windows/install.pp#L38-L48
[3]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/templates/install_puppet.bat.erb
[4] https://forge.puppetlabs.com/opentable/puppetversion

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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.

--
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Bird discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird>
*
*—**save $249!*

--
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 [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMJiBK7vUAyC-8Y6qxzZ%2BYjfVuJo49iyBXvinZv_2g%2B3AK3dWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

reply | permalink

Rob Reynolds

at Jul 17, 2015 at 9:55 pm

⇧

On Fri, Jul 17, 2015 at 4:38 PM, Rob Reynolds wrote:

On Fri, Jul 17, 2015 at 8:34 AM, Byron Miller wrote:

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?

This is most assuredly not intended. I can say that we don't really
support using puppet to upgrade puppet - because file locking on Windows.
It appears you have run into this. We have an upcoming epic for this in
MODULES-2040[1], which will be similar to how Puppetlabs-Puppet_Agent will
handle upgrades for WIndows agents[2][3].

I would highly suggest that you follow suit on those ideas until something
is in place or upgrade out of band e.g. use something besides Puppet to
upgrade Puppet on Windows. You can also try using the puppetversion
module[4].

[1] https://tickets.puppetlabs.com/browse/MODULES-2040
[2]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/manifests/windows/install.pp#L38-L48
[3]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/templates/install_puppet.bat.erb
[4] https://forge.puppetlabs.com/opentable/puppetversion

Also, anyone interested in looking at the MODULES-2040 approach should
definitely read my comment[1] on known issues migrating the puppet_agent
code over to a more generalized approach.

[1]
https://tickets.puppetlabs.com/browse/MODULES-2040?focusedCommentId=190065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-190065

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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.

--
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Bird discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird> *
*—**save $249!*

--
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Bird discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird>
*
*—**save $249!*

--
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 [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMJiBK6iDvVv8dpDsL_Oa3bRBef5VyF%2BPNc%3DYnxnSo9uBEWoSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

reply | permalink

Rob Reynolds

at Jul 17, 2015 at 10:30 pm

⇧

The ruby executable locking was likely exasperated by the wrong version of
ruby in 3.7.5 - we've yanked the 3.7.5 release[1] based on what we've
discovered this afternoon.

[1]
https://groups.google.com/forum/#!msg/puppet-dev/VtqadVFJKLM/e28O_so11fMJ
<https://groups.google.com/forum/m/?utm_medium=email&utm_source=footer#!msg/puppet-dev/VtqadVFJKLM/e28O_so11fMJ>

On Friday, July 17, 2015, Rob Reynolds wrote:

On Fri, Jul 17, 2015 at 4:38 PM, Rob Reynolds <[email protected]
wrote:

On Fri, Jul 17, 2015 at 8:34 AM, Byron Miller <[email protected]
wrote:

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?

This is most assuredly not intended. I can say that we don't really
support using puppet to upgrade puppet - because file locking on Windows.
It appears you have run into this. We have an upcoming epic for this in
MODULES-2040[1], which will be similar to how Puppetlabs-Puppet_Agent will
handle upgrades for WIndows agents[2][3].

I would highly suggest that you follow suit on those ideas until
something is in place or upgrade out of band e.g. use something besides
Puppet to upgrade Puppet on Windows. You can also try using the
puppetversion module[4].

[1] https://tickets.puppetlabs.com/browse/MODULES-2040
[2]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/manifests/windows/install.pp#L38-L48
[3]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/templates/install_puppet.bat.erb
[4] https://forge.puppetlabs.com/opentable/puppetversion

Also, anyone interested in looking at the MODULES-2040 approach should
definitely read my comment[1] on known issues migrating the puppet_agent
code over to a more generalized approach.

[1]
https://tickets.puppetlabs.com/browse/MODULES-2040?focusedCommentId=190065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-190065

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+[email protected]
<javascript:_e(%7B%7D,'cvml','puppet-users%[email protected]');>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.

--
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Bird discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird> *
*—**save $249!*

--
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Bird discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird>
*
*—**save $249!*

--
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 [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMJiBK5HhJ6z7_KpZNyxTGHLhWwzUYuJUzRZOA%3D%2BA3zU-gXDTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

reply | permalink

Rob Reynolds

at Jul 24, 2015 at 2:42 pm

⇧

On Fri, Jul 17, 2015 at 5:30 PM, Rob Reynolds wrote:

The ruby executable locking was likely exasperated by the wrong version of
ruby in 3.7.5 - we've yanked the 3.7.5 release[1] based on what we've
discovered this afternoon.

[1]
https://groups.google.com/forum/#!msg/puppet-dev/VtqadVFJKLM/e28O_so11fMJ
<https://groups.google.com/forum/m/?utm_medium=email&utm_source=footer#!msg/puppet-dev/VtqadVFJKLM/e28O_so11fMJ>

On Friday, July 17, 2015, Rob Reynolds wrote:

On Fri, Jul 17, 2015 at 4:38 PM, Rob Reynolds wrote:

On Fri, Jul 17, 2015 at 8:34 AM, Byron Miller wrote:

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?

This is most assuredly not intended. I can say that we don't really
support using puppet to upgrade puppet - because file locking on Windows.
It appears you have run into this. We have an upcoming epic for this in
MODULES-2040[1], which will be similar to how Puppetlabs-Puppet_Agent will
handle upgrades for WIndows agents[2][3].

I would highly suggest that you follow suit on those ideas until
something is in place or upgrade out of band e.g. use something besides
Puppet to upgrade Puppet on Windows. You can also try using the
puppetversion module[4].

[1] https://tickets.puppetlabs.com/browse/MODULES-2040
[2]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/manifests/windows/install.pp#L38-L48
[3]
https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/templates/install_puppet.bat.erb
[4] https://forge.puppetlabs.com/opentable/puppetversion

As a followup, it appears puppetversion module doesn't allow the upgrades
to happen successfully. We're looking at other possibilities for folks to
try currently, including using PsExec[1] to resend the msiexec install
command.

[1] https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

Also, anyone interested in looking at the MODULES-2040 approach should
definitely read my comment[1] on known issues migrating the puppet_agent
code over to a more generalized approach.

[1]
https://tickets.puppetlabs.com/browse/MODULES-2040?focusedCommentId=190065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-190065

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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/ab190044-e33f-45bd-8948-6160c251243d%40googlegroups.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.

--
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Bird discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird> *
*—**save $249!*

--
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Bird discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird>
*
*—**save $249!*

--
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 [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMJiBK7o5HMSY%3DigPRd1g1ZPQ%3D4shzcKR0T_2zToW1PRiMQJEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

reply | permalink

group	puppet-users @
categories	puppet
posted	Jul 17, '15 at 12:59p
active	Jul 24, '15 at 2:42p
posts	8
users	4
website	puppetlabs.com

responses	expanded	Hotkey: s
font	variable	Hotkey: f
user style	avatars	Hotkey: a

[Puppet Users] Cannot update Puppet 3.7.5 to 3.8.1 on Windows

Search Discussions

Related Discussions

4 users in discussion