ReleaseEngineering/How To/Set Up a Freshly Imaged Slave: Difference between revisions

ReleaseEngineering/How To/Set Up a Freshly Imaged Slave (view source)

640 bytes removed , 12 July 2013

Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti

1,529

edits

@@ Line 87: / Line 87: @@
 ** once puppet hits the right master, it will both blow away the certificates (even though they were correct) and reboot.  So you'll need to wait for a restart, log in, and go through the above process again.  Hopefully you'll only need to do this once.
 * once puppet is done eviscerating itself, have a look at the slave's twistd.log.  If it's getting an UnauthorizedLogin for connection to the staging master, fix the password or add the slave to the master's config.  Otherwise, watch the staging master until the slave finishes a job.
-= Bld-Lion-r5 -- buildbot startup failures on Lion =
-* see [https://bugzilla.mozilla.org/show_bug.cgi?id=858040 bug 858040] for details
-* redux: Lion is still on the old puppet, and there is a dependency issue between python and buildbot. You need to remove the existing copy of buildbot, re-run puppet to re-install buildbot using the newer version of python, and the reboot the slave. The commands to do this are:
- # As root
- rm -rf /var/db/.puppet_pkgdmg_installed_buildbot*
- rm -rf /tools/buildbot*
- /usr/bin/puppetd --onetime --no-daemonize --logdest console \
-   --server scl3-production-puppet.srv.releng.scl3.mozilla.com
- # reboot
 = How to fix the hostname for Windows =
 Instead of replicating the information. Here are the instructions for all of our Windows platforms.