Upgrade puppet from EPEL to Puppet Labs

I've made two attempts to upgrade puppet on my puppetmaster and I can't get
everything talking with foreman. I'm running everything from one server,
the foreman server is also the puppetmaster. Server is running RHEL 6.5,
currently running Foreman 1.3 which was installed fresh about a month ago.

I started by adding the puppetlabs yum repo to the server and running

yum update puppet-server

I had to edit the sudoers file to accommodate for puppetca no longer being
a valid command. After a few hours when I open up foreman dashboard I see
my hosts are out of sync. Seems like the puppet agents are running off a
cached configuration. Logs on the server are not providing much
information. Where should I be looking for check-ins by the agents? I
looked at wireshark output and can see communication between agent and
master but the conversation looks short.

What process should I follow to update from EPEL puppet to PuppetLabs
puppet on my server? Do I need to change anything in foreman after doing
this? What logs should I be looking at for information?

The only two things you should need to do are to update sudoers (as
you've done) and update config.ru for the puppetmaster. Details here:

http://projects.theforeman.org/projects/foreman/wiki/FAQ#Upgrade-puppet-from-v2-to-v3-gotchas

If that doesn't work, the first place to look is the agent logs. Either
check syslog on your agents, or run "puppet agent -t" and check the output.

If they successfully download a catalog and apply it, but still show out
of sync in Foreman, then it's likely that reports between the master and
Foreman aren't working.

··· On 19/02/14 00:37, zjherner@gmail.com wrote: > I've made two attempts to upgrade puppet on my puppetmaster and I can't > get everything talking with foreman. I'm running everything from one > server, the foreman server is also the puppetmaster. Server is running > RHEL 6.5, currently running Foreman 1.3 which was installed fresh about > a month ago. > > I started by adding the puppetlabs yum repo to the server and running > > # yum update puppet-server > > I had to edit the sudoers file to accommodate for puppetca no longer > being a valid command. After a few hours when I open up foreman > dashboard I see my hosts are out of sync. Seems like the puppet agents > are running off a cached configuration. Logs on the server are not > providing much information. Where should I be looking for check-ins by > the agents? I looked at wireshark output and can see communication > between agent and master but the conversation looks short. > > What process should I follow to update from EPEL puppet to PuppetLabs > puppet on my server? Do I need to change anything in foreman after > doing this? What logs should I be looking at for information?


Dominic Cleal
Red Hat Engineering