Due to a failed reconfig, master buildbot-master68 needs to be restarted

RESOLVED FIXED

Status

Release Engineering
Buildduty
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: simone, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
In particular, the master has been double reconfig's, so a graceful restart is needed.
steps to make this happen:

1) disable master in slavealloc

2) (using fabric/manage_masters) run:
    a) python manage_masters.py -f production-masters.json -H bm68-tests1-linux64 graceful_restart

simone had a good idea to run this on screen in case he goes offline. I think we can can call manage_masters from cruncher?
(Reporter)

Comment 2

3 years ago
Callek's advice, actually (screen somewhere) ;-)
Master is already disabled in slavealloc.

I am going to run the command on cruncher.
(Reporter)

Comment 3

3 years ago
graceful restart is now running in a screen on cruncher
(Reporter)

Comment 4

3 years ago
Graceful restart completed:

[OK] finished gracefully restarting of buildbot-master68.srv.releng.usw2.mozilla.com:/builds/buildbot/tests1-linux64

The master has also been re-enabled in slavealloc.
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.