Jira (PUP-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Nikolai R Kristiansen commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Are you planning to support the upgrade path from distro packages to PC1 packages? If not, we will have to change our install prosess. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Nikolai R Kristiansen commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Just a note on the upgrade path. We use pxe with preseed to install ubuntu on new desktops. The last step of the pxe-install is to install the distro version of puppet, and after the new node being autosigned, it should upgrade itself. Do you suggest installing the 4.x puppet-agent from puppetlabs directly instead? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Nikolai R Kristiansen commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Henrik Lindberg I see my understanding is lacking, of course it only runs master side. I can't test it right away, but this is probably happening because puppetserver was not upgraded to the latest version as the puppet-agent was. I'll post back. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Nikolai R Kristiansen created an issue Puppet / PUP-6638 create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Issue Type: Bug Assignee: Unassigned Created: 2016/08/18 1:39 PM Priority: Normal Reporter: Nikolai R Kristiansen When trying to upgrade from the default puppet version on Ubuntu 16.04 (http://packages.ubuntu.com/xenial/puppet 3.8.x) to the latest PC1 puppet-agent package using the puppetlabs-puppet_agent module we get the following error: Evaluation Error: Error while evaluating a Function Call, uninitialized constant Puppet::Pops::PuppetStack at ... The culprint was the usage of the Puppet::Pops::PuppetStack.stacktrace (https://github.com/puppetlabs/puppet/commit/2211c646921f85a31611f018cd8bfaab76692c98) in create_resource (https://github.com/puppetlabs/puppet/commit/01db61e24178a3baebbeaa1c58250fcbf447d8bc) which is called in the initialization of puppetlabs-apt in turn used by the puppetlabs-puppet_agent. This looks like a regression. Is it possible to only run the stacktrace generating code on 4.x agents?
