Now that the kernel upgrades have been pushed out, there are still a handful of servers that need a reboot. slaveapi1.srv.releng.scl3.mozilla.com releng-puppet1.srv.releng.scl3.mozilla.com releng-puppet2.srv.releng.scl3.mozilla.com signing4.srv.releng.scl3.mozilla.com signing5.srv.releng.scl3.mozilla.com signing6.srv.releng.scl3.mozilla.com proxxy1.srv.releng.use1.mozilla.com proxxy1.srv.releng.usw2.mozilla.com proxxy1.srv.releng.scl3.mozilla.com ubuntu64packager1.srv.releng.use1.mozilla.com
releng-puppet* can be rebooted one at a time with no impact. signing* can be rebooted one at a time with no impact (but notify buildduty first). proxxy* can be rebooted simultaneously with no impact (I think; ask catlee) ubuntu64packager1 can be rebooted at will; just let anyone currently logged in know in advance. And halt it afterward, unless someone needs to get back in immediately.
Proxxy systems have been rebooted proxxy1.srv.releng.use1.mozilla.com proxxy1.srv.releng.usw2.mozilla.com proxxy1.srv.releng.scl3.mozilla.com
releng-puppet1.srv.releng.scl3.mozilla.com - done ubuntu64packager1.srv.releng.use1.mozilla.com is not a normal instance and seems to be using a legacy version of grub. As Dustin suggested, we should probably rebuild it with a current ami
Signing servers are done. signing4.srv.releng.scl3.mozilla.com signing5.srv.releng.scl3.mozilla.com signing6.srv.releng.scl3.mozilla.com and releng-puppet2.srv.releng.scl3.mozilla.com done also
slaveapi1.srv.releng.scl3.mozilla.com - done
I think the proxxy instances were rebooted. Did you resolve what needed to happen wrt. their hostnames?
I think you're asking about the other, un-puppeted proxxy instances. I just terminated those on an irc OK.
(In reply to Chris AtLee [:catlee] from comment #6) > I think the proxxy instances were rebooted. Did you resolve what needed to > happen wrt. their hostnames? Most of the work here is done. Yes, the proxxy aws instances needed their hostnames set after a reboot. I've filed bug1134468 to address that. I've also filed bug1134467 to deal with rebuilding ubuntu64packager1. r/f everything else
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.