On Wed, Dec 3, 2014 at 9:43 AM, Jason Chinsen <[email protected]> wrote:
> Hello There, > > We started our puppet adventures at 3.2.x with both windows and linux > boxes. Since then we have upgraded our Master to 3.3.2 and are looking to > upgrade to 3.7. The linux agent upgrades are very simple, but I am running > into issues with the windows agent upgrades :/ We have an Artifcatory based > Nuget repo and all of the pipping is working. It looks like chocolatey is > running an upgrade and it is not working. (it could very well be my nuget > code :) as I am not a windows guy) > Trying to upgrade Puppet with Puppet on Windows is harder because Windows locks files that are in use instead of letting you replace them in place. There is a module from OpenTable (puppetversion[1]) that may need some work to support the upgrade of PE agents as well, but it does a good job of upgrading out of band. [1] https://forge.puppetlabs.com/opentable/puppetversion > > > This is the output of the puppet run: > Debug: Executing 'C:\ProgramData\chocolatey\chocolateyInstall\chocolatey.cmd > update pe-agent -source nuget-repo'; > > Notice: /Stage[main]/Puppet_enterprise_agent_upgrade/Package[pe-agent]/ > ensure: created > > Debug: /Stage[main]/Puppet_enterprise_agent_upgrade/Package[pe-agent]: The > container Class[Puppet_enterprise_agent_upgrade] will propagate my > refresh event > > And this is the output of the chocolatey run manually: > > C:\ProgramData\chocolatey\chocolateyInstall\chocolatey.cmd update pe-agent > -source nuget-repo > > Nothing to update. > > Use -force. It may think things are good to go as it didn't detect errors. > When I run an install vs upgrade it works as planned, with one lingering > affect, where puppet tries to change 3.3.2 to latest all the time (this I > can likely fix in the puppet manifest with a version number vs latest) > Debug: Executing > 'C:\ProgramData\chocolatey\chocolateyInstall\chocolatey.cmd upd > ate pe-agent -source nuget-repo' > Notice: > /Stage[main]/Puppet_enterprise_agent_upgrade/Package[pe-agent]/ensure: e > nsure changed '3.3.2' to 'latest' > Debug: /Package[pe-agent]: The container > Class[Puppet_enterprise_agent_upgrade] > will propagate my refresh event > > > This could be an issue with the provider itself. Would you follow up with a note on puppet-chocolatey[2]? [2] https://github.com/chocolatey/puppet-chocolatey/issues > Any help would be great > Thanks, > Jason. > > -- > 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/8be76ca0-4b98-494d-834a-2c910be423bd%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/8be76ca0-4b98-494d-834a-2c910be423bd%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Rob Reynolds Developer, Puppet Labs *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * http://2015.puppetconf.com/ *Register early to save 40%!* -- 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/CAMJiBK53VLQOATJDXQ1YdehXpOhhugMUnf5mG8Wsc0iwDeZ2PA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
