Closed
Bug 837168
Opened 11 years ago
Closed 11 years ago
puppetize.sh should specify the puppet version
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
Attachments
(1 file)
1.71 KB,
patch
|
rail
:
review+
|
Details | Diff | Splinter Review |
I mirrored the puppetlabs repo, bringing it up to 3.0.2. This doesn't cause problems for running systems, but when puppetizing a new host, puppetize.sh just runs yum install puppet which gets 3.0.2, which doesn't work with the current masters.
Assignee | ||
Comment 1•11 years ago
|
||
Sorry, this is in the kickstart scripts, not puppetize.sh.
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #709108 -
Flags: review?(rail)
Assignee | ||
Comment 3•11 years ago
|
||
Fixed in the kickstart scripts on the PXE servers (well, committed to puppet - it will be fixed in an hour or so)
Comment 4•11 years ago
|
||
Comment on attachment 709108 [details] [diff] [review] bug837186.patch lgtm
Attachment #709108 -
Flags: review?(rail) → review+
Assignee | ||
Comment 5•11 years ago
|
||
landed - thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•