798414 - Upgrade PuppetAgain to Puppet 3.0

Status: RESOLVED DUPLICATE of bug 825056

(Infrastructure & Operations :: RelOps: General, task)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

I think we're in good shape, but we need to assure ourselves of that and then make the leap to Puppet-3.0.x

Comment 1

[Rail Aliiev [:rail]]

Wooohoo!

Dustin, do you have a plan or a checklist how we should test it?

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Not yet.  I'll put it here when I do.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

If only I had the time!

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

I built a 3.0.2 RPM, patched for 
 * https://projects.puppetlabs.com/issues/17864
 * https://projects.puppetlabs.com/issues/15561

and put it on relabs08.  It seemed to work.  I'd like to get a master running that version, too -- that will be relabs06.  However, the instructions for getting a standalone master running need some brushing-up.  I'll work through it and document what I find.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

[root@relabs08 ~]# puppet agent --test --server=relabs06.build.mtv1.mozilla.com
Info: Retrieving plugin
Info: Caching catalog for relabs08.build.mtv1.mozilla.com
Info: Applying configuration version '1357331681'
Notice: Finished catalog run in 0.10 seconds
[root@relabs08 ~]# puppet --version
3.0.2

That's an empty manifest, and against a standalone master (so no cert chaining), but still.. progress!

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

OK, I was able to build all of the various server types with patched 3.0.2 on both the client and master.

Now we need to figure out if we're going to try to implement 3.0.2 in infra puppet or puppetagain.

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

This will be done as part of bug 825056, with Puppet-3.2.0 (not yet released)