Closed Bug 1068170 Opened 10 years ago Closed 10 years ago

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

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: sbruno, Unassigned)

Details

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?
Callek's advice, actually (screen somewhere) ;-)
Master is already disabled in slavealloc.

I am going to run the command on cruncher.
graceful restart is now running in a screen on cruncher
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
Closed: 10 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.