pe_repo - upgrade agents via puppet agent -t when the master is upgraded. - broken.

[Brett Swift]

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? 

[Rob Nelson]

Brett, I haven't used it, but rather than using an exec, Puppet recommends using https://forge.puppet.com/puppetlabs/puppet_agent. I was actually just reading docs at https://docs.puppet.com/pe/2015.3/install_upgrading_agents.html#upgrade-agents-to-pe-20153-from-38x because we're going to be doing the 2015->2016 upgrade soon ourselves.

Rob Nelson
rnel...@gmail.com

--
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...@googlegroups.com.
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.

[Brett Swift]

That's if you're moving from a PE 3.8 infrastructure as per the 2016.1.1 docs though. Unless I'm reading that wrong.

From a 2015.2.x to 2016 it suggests pe_repo if it's in a puppet enterprise installation.

Did I miss something here?

You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ngjE0C0Uj30/unsubscribe.
To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAC76iT_KWEFRt87JL4HDGMd6uMcbH6Pek9BWNifNttCZBzp%3DMQ%40mail.gmail.com.

[Rob Nelson]

My bad, I gave a naive read through and didn't see that 2015->2016 is not yet supported. Nothing to see here...

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2BWrF%2BgNwRd%2Bhj-czFJ0Ghbe5HPhpB_ZNo%2BD8hQC%2BVam%3DF-F7g%40mail.gmail.com.

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

--

Rob Nelson
rnel...@gmail.com