1220116 - releng changes to decommission t-yosemite-r5-0092

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Comment 1

[Alin Selagea [:aselagea]]

Attachment: bug1220116.patch

Two things to mention here:
   1. t-yosemite-r5-0029 appears as removed from the current version of production_config.py, however it is still present in slave health and slavealloc (enabled and working fine), so I corrected this in the patch.
   2. t-yosemite-r5-0042 has been decommissioned (see bug 1178442), the change is present in slavealloc, but not in production_config.py. Corrected this in the patch as well.

Comment 2

[Alin Selagea [:aselagea]]

Noticed that t-yosemite-r5-0042 hasn't been removed from slavealloc (it is only marked as "decommed" in slavealloc):

mysql> select slaveid, name, speedid, locked_masterid, enabled, current_masterid, notes from slaves where name = 't-yosemite-r5-0042' or name = 't-yosemite-r5-0092';
+---------+--------------------+---------+-----------------+---------+------------------+----------+
| slaveid | name               | speedid | locked_masterid | enabled | current_masterid | notes    |
+---------+--------------------+---------+-----------------+---------+------------------+----------+
|   22622 | t-yosemite-r5-0042 |       8 |            NULL |       0 |              295 | decommed |
|   22732 | t-yosemite-r5-0092 |       8 |            NULL |       0 |              297 | decommed |
+---------+--------------------+---------+-----------------+---------+------------------+----------+
2 rows in set (0.00 sec)

I guess I can go on and remove the two slaves from slavealloc, right?

Comment 3

[Alin Selagea [:aselagea]]

Slave has been decommissioned.

Comment 4

[Release Engineering SlaveAPI Service]

In production: https://hg.mozilla.org/build/buildbot-configs/rev/a998ce105f15

Comment 5

[Release Engineering SlaveAPI Service]

In production: https://hg.mozilla.org/build/buildbot-configs/rev/5d6695abf718