Closed Bug 1396454 Opened 3 years ago Closed 3 years ago

t-xp32-ix-001 is unreachable

Categories

(Infrastructure & Operations :: DCOps, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: slaveapi, Assigned: van)

References

Details

Attachments

(2 files)

No description provided.
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?
Assignee: server-ops-dcops → vle
Flags: needinfo?(mcornmesser)
XP machines can no longer be reimaged since opsec has asked that we tighten security. This machine should probably be decommissioned instead.
can you decommission this one too please? i've taken it offline.
Flags: needinfo?(mcornmesser) → needinfo?(spacurar)
@van: can you please decommssion this in inventroy.
Flags: needinfo?(spacurar) → needinfo?(vle)
Deleted from nagios4.
Attachment #8905522 - Flags: review?(mtabara)
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.
decommissioned in inventory.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(vle)
Resolution: --- → FIXED
Attachment #8905522 - Flags: review?(mtabara)
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?
Attachment #8905522 - Flags: feedback?(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.
Attachment #8905522 - Flags: feedback?(aselagea) → checked-in+
Attached patch bb-configs.patchSplinter Review
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.
Attachment #8908117 - Flags: review?(mtabara)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Also did some cleaning in slavealloc. This should be done once we land the patch above.
Attachment #8908117 - Flags: review?(mtabara) → review+
(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.
(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
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.
Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
(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!
You need to log in before you can comment on or make changes to this bug.