Closed
Bug 567205
Opened 16 years ago
Closed 16 years ago
audit that try slaves sync up after reboots with the puppet server
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: lsblakk)
Details
(Whiteboard: [buildslaves][puppet])
Attachments
(3 files)
|
180.92 KB,
text/plain
|
Details | |
|
1.47 KB,
text/plain
|
Details | |
|
1.36 KB,
patch
|
bear
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
I made one of the try slaves that used to be in the sandbox network to sync up with puppet and there was a lot of output and an error in the log. Since they have been recloned they are up-to-date but we should ensure that they don't fall out of sync again.
| Reporter | ||
Comment 1•16 years ago
|
||
Updated•16 years ago
|
Priority: -- → P3
Hardware: x86 → All
Updated•16 years ago
|
Whiteboard: [buildslaves][puppet]
Updated•16 years ago
|
Assignee: nobody → bear
Comment 4•16 years ago
|
||
Manually created the buildbot-0.8.0pre directory and ensured the symlink and semaphore file are present.
I will be researching this further with bhearsum in the morning to find out why puppet is refusing to let buildbot play in the try-mac-slave* playground.
Applied to the following slaves:
try-mac-slave{02,03,04,06,07,08,09,10,11,12,13,14,16,17,18,19}
Comment 6•16 years ago
|
||
Turns out that the case statements weren't using regex properly. Here's the more explicit way, fully tested.
Attachment #447327 -
Flags: review?(bear)
Updated•16 years ago
|
Attachment #447327 -
Flags: review?(bear) → review+
Comment 7•16 years ago
|
||
Comment on attachment 447327 [details] [diff] [review]
fix case's in install package
changeset: 159:05641475c4ab
Attachment #447327 -
Flags: checked-in+
Comment 8•16 years ago
|
||
Mac problems should be fixed, back to lsblakk per bear.
Assignee: bhearsum → lsblakk
| Assignee | ||
Comment 9•16 years ago
|
||
Yup - confirmed that all mac try slaves are back online and coming back after reboots. Thanks for everyone's part in getting this fixed.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•