Closed
Bug 1019667
Opened 12 years ago
Closed 12 years ago
Configure DS to install puppet-3.6.1 and, where required, json_pure
Categories
(Infrastructure & Operations :: RelOps: Puppet, task)
Infrastructure & Operations
RelOps: Puppet
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
Currently it's installing 3.4.2 and upgrading from there on the first run, which will work but is inefficient.
| Assignee | ||
Comment 1•12 years ago
|
||
I'll do this after the move trains are complete.
| Assignee | ||
Updated•12 years ago
|
Blocks: bld-lion-r5-068
| Assignee | ||
Comment 2•12 years ago
|
||
We might need to do this sooner - the manifests now don't run with puppet 3.2.2, so the upgrade no longer works.
| Assignee | ||
Comment 3•12 years ago
|
||
On both install.{build,test}.releng.scl3, I:
Move /Deploy/Packages/Puppet to Puppet-3.2.2
Put puppet-3.6.1.pkg and facter-1.7.5.pkg in /Deploy/Packages/Puppet
Added /Deploy/Packages/JsonPure
On install.build, I verified that the bld-lion workflow is still pointing to "Puppet" and rebooted bld-lion-r5-068.
bld-lion-r5-068:~ root# puppet --version
3.6.1
So that's a victory.
On install.test, I added a step to install JsonPure to the Mountan Lion and Snow workflows.
I reimaged t-snow-r4-0138 (bug 1025098) to see if that works.
| Assignee | ||
Comment 4•12 years ago
|
||
t-snow-r4-0138:~ root# puppet --version
3.6.1
Having done the identical for mountain lion, I'm going to assume this is all good. If mountain lion deploys fail, we'll know what happened.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•