1132989 - reboot misc servers for kernel upgrades

Status: RESOLVED FIXED

Description

[Jake Watkins [:dividehex]]

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

Comment 1

[Dustin J. Mitchell [:dustin] pronoun: he]

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.

Comment 2

[Jake Watkins [:dividehex]]

Proxxy systems have been rebooted

proxxy1.srv.releng.use1.mozilla.com
proxxy1.srv.releng.usw2.mozilla.com
proxxy1.srv.releng.scl3.mozilla.com

Comment 3

[Jake Watkins [:dividehex]]

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

Comment 4

[Jake Watkins [:dividehex]]

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

Comment 5

[Jake Watkins [:dividehex]]

slaveapi1.srv.releng.scl3.mozilla.com - done

Comment 6

[Chris AtLee [:catlee]]

I think the proxxy instances were rebooted. Did you resolve what needed to happen wrt. their hostnames?

Comment 7

[Dustin J. Mitchell [:dustin] pronoun: he]

I think you're asking about the other, un-puppeted proxxy instances.  I just terminated those on an irc OK.

Comment 8

[Jake Watkins [:dividehex]]

(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