Page MenuHomePhabricator

decom furud
Closed, ResolvedPublic


remove furud from all the places, dont forget to shutdown/destroy the VM, stored configs/ icinga, salt...DNS..


Event Timeline

furud was meant to replace antimony but plans changed and it's not going to be used now

related: T123718, T111465, T137224

Change 293129 had a related patch set uploaded (by Dzahn):
decom furud

root@palladium:~# puppetstoredconfigclean.rb furud.codfw.wmnet
Killing furud.codfw.wmnet...done.

[palladium:~] $ sudo puppet cert clean furud.codfw.wmnet
Notice: Revoked certificate with serial 1602

[neodymium:~] $ sudo salt-key -d furud.codfw.wmnet
The following keys are going to be deleted:

root@furud:~# shutdown -h now
W: molly-guard: SSH session detected!

[ganeti2001:~] $ sudo gnt-instance remove furud.codfw.wmnet
This will remove the volumes of the instance furud.codfw.wmnet
(including mirrors), thus removing all the data of the instance.

y/[n]/?: y

Tue Jun 7 17:50:41 2016 - WARNING: Could not remove disk 1 on node ganeti2003.codfw.wmnet, continuing anyway: Error 28: Operation timed out after 900023 milliseconds w
ith 0 bytes received
Failure: command execution error:
Can't remove instance's disks
[ganeti2001:~] $

furud.codfw.wmnet kvm debootstrap+default ganeti2003.codfw.wmnet ERROR_down -

@akosiaris have you seen the problem above before when deleting VMs? ^

furud is still showing pending salt key acceptance on the salt master.

@RobH thanks, the accepted key was deleted, then this got recreated because it was still running. it's in an "ERROR_down" state now after the error above.. hmm

i simply repeated the same gnt-instance remove command today and it was immediately done, no issues at all.. shrug

@akosiaris have you seen the problem above before when deleting VMs? ^

No, but then again we haven't been deleting VMs much yet. I am not sure what that is, but it might be a network issue. Perhaps some port ferm misconfiguration. I 'll have a look.