I'm trying to wrap my head around how you would use puppet to upgrade agents. Maybe my assumptions on how this 'should' work are wrong.
I just migrated a puppet agent from a 2015.2.3 master to a 2016.1.1 master. I signed the cert on the new master and no dice on the upgrade. The documentation here: https://docs.puppet.com/pe/latest/install_upgrading_agents.html#upgrade-agents-to-pe-201611-from-201533 ... seems to be anti-puppet mentality, because it is asking you to go through the package installation script to upgrade your agents. This doesn't seem right, I don't want to configure an exec command to run a curl script. And yum update puppet-agent isn't working.. as you'll see why below. Also - the pe_repo entry shows this: baseurl=https: //devcorepptl003.matrix.sjrb.ad:8140/packages/2015.2.3/el-6-x86_64 They point directly to 2015.2.3, and the "new master" which is devcorepptl918.matrix.sjrb isn't reflected in the pe_repo class. I'm guessing I need to supply the pe_repo class values, but shouldn't it get this from facter and be auto-magical? My assumed process: 1) migrate a puppet agent from a 2015.2.3 master, to a 2016.1.1 master. 2) run puppet agent -t 3) expect to see the agent upgrade. But that isn't the case.. If I change the pe_repo.repo file manually to point to my new master and configure the newer version of puppet, and do a `yum upgrade puppet_agent` it will offer me an upgrade to 1.4.1. I found the pe_repo class and the puppet_enterprise class on the new master but it's not yet obvious how I should manipulate it to execute an agent upgrade? -- 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/950e1316-d8c2-48f6-8377-7cb6ae3ee952%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
