Closed
Bug 704976
Opened 13 years ago
Closed 11 years ago
After re-imaging a slave should be able to connect to puppet/opsi with no human intervention
Categories
(Release Engineering :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: armenzg, Unassigned)
Details
(Whiteboard: [slaveminator])
Currently there are some manual steps needed to make a slave sync up with puppet/opsi correctly. Unfortunately even the manual steps are not very clear since we have to run them several times until it eventually works: https://wiki.mozilla.org/ReleaseEngineering/How_To/Set_Up_a_Freshly_Imaged_Slave#puppet There is also the work of setting the hostname automatically (bug 704975) for the machine which has lower priority than this work (as it currently takes more manual and debugging work that setting the hostname). I will use [slaveminator] as a whiteboard tag to keep track of any bugs that optimize the setup and maintenance of our pool of slaves. There are other projects like "buildbot start" check that should take higher priority that this work.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 1•11 years ago
|
||
We're still missing the key management part (tracked elsewhere), but WONTFIXing mostly for the OPSI part.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•