1396454 - t-xp32-ix-001 is unreachable

Status: RESOLVED FIXED

(Infrastructure & Operations :: DCOps, task)

Comment 1

[Van Le [:van]]

this host was recently reimaged but during the reimaging process, it asked me to join the domain. there was no password so i had to join the workgroup instead. i believe this is blocking something as the host is pingable but not sshable, same thing as t-xp32-ix-002. any ideas?

Comment 2

[Amy Rich [:arr] [:arich]]

XP machines can no longer be reimaged since opsec has asked that we tighten security. This machine should probably be decommissioned instead.

Comment 3

[Van Le [:van]]

can you decommission this one too please? i've taken it offline.

Comment 4

[Sebastian Pacurar [:spacurar]]

@van: can you please decommssion this in inventroy.

Comment 5

[Sebastian Pacurar [:spacurar]]

Attachment: puppet-xp-001.patch

Deleted from nagios4.

Comment 6

[Sebastian Pacurar [:spacurar]]

Deleted from buildslaves as well. Should there be anything else to be done? I couldn't find anything in buildbot. Correct me if I am wrong.

Comment 7

[Van Le [:van]]

decommissioned in inventory.

Comment 8

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 8905522 [details] [diff] [review]
puppet-xp-001.patch

@aselagea: do we still need this puppet patch or are we all good with this?

Comment 9

[Alin Selagea [:aselagea]]

Comment on attachment 8905522 [details] [diff] [review]
puppet-xp-001.patch

It seems the patch has already been pushed, so that part is done.

Comment 10

[Alin Selagea [:aselagea]]

Attachment: bb-configs.patch

Some bb-configs cleaning. 
Since t-xp32-ix-001 and t-xp32-ix-002 were decommed, only machines in range [003-010] are still in use for XP so I removed the rest of them from bb-configs.

Comment 11

[Alin Selagea [:aselagea]]

Also did some cleaning in slavealloc. This should be done once we land the patch above.

Comment 12

[Mihai Tabara [:mtabara]⌚️GMT]

(In reply to Alin Selagea [:aselagea][:buildduty] from comment #11)
> Also did some cleaning in slavealloc. This should be done once we land the
> patch above.

Please reference any other patches that land here as well. I intend to use this bug as a good documentation skeleton for decommissioning slaves.

Comment 13

[Alin Selagea [:aselagea]]

Comment on attachment 8908117 [details] [diff] [review]
bb-configs.patch

https://hg.mozilla.org/build/buildbot-configs/rev/6d6b4125be72
https://hg.mozilla.org/build/buildbot-configs/rev/8f12acd50578

Comment 14

[Alin Selagea [:aselagea]]

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #12)

> Please reference any other patches that land here as well. I intend to use
> this bug as a good documentation skeleton for decommissioning slaves.

There several places to do changes for this:
    - inventory - :van marked these machines as decommissioned
    - Nagios - see the patch attached by Sebastian [1]
    - bb-configs - see the patch I attached above [2]
    - slavealloc - we just need some simple commands to remove these entries from DB. 

e.g. mysql> select * from slaves where name like "t-xp32-ix%" and convert(substring(name, -3), unsigned integer) > 010;
     ...
     mysql> delete from slaves where name like "t-xp32-ix%" and convert(substring(name, -3), unsigned integer) > 010;
     Query OK, 30 rows affected (0.02 sec)
  
[1] https://bugzilla.mozilla.org/attachment.cgi?id=8905522
[2] https://bugzilla.mozilla.org/attachment.cgi?id=8908117

Comment 15

[Mihai Tabara [:mtabara]⌚️GMT]

I think this is done now. Thanks for previous comment, that's gonna be a good resource for docs.
Please reopen if I'm wrong.

Comment 16

[Mihai Tabara [:mtabara]⌚️GMT]

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #15)
> I think this is done now. Thanks for previous comment, that's gonna be a
> good resource for docs.
> Please reopen if I'm wrong.

For the record, Andrei has added the docs here - https://wiki.mozilla.org/ReleaseEngineering/How_To/Decommission_Slave
Thanks!