decomission worker0.staging
Inventory:
Summary: Decommission a node is a multiple process steps which impacts repositories and inventory references.
Tasks:
- Update puppet swh-site node references (if any)
- Actually decomission the node (+ commit/push if within sysadm-provisioning)
-
Update inventory references
- delete or deactivate the node(s)
- Deprecate or delete the ip addresses
-
Decommission node reference(s) in puppet master
root@pergamon# swh-puppet-master-decommission <node_0> ...<node_n> - puppet run to drop the icinga alert ^
Activity
changed milestone to %MRO 2023
added activity::MRO label
decommission start:
root@worker0:~# puppet agent --disable 'swh/infra/sysadm-environment#4818: decomission' root@pergamon:~# swh-puppet-master-decommission worker0.internal.staging.swh.network + puppet node deactivate worker0.internal.staging.swh.network Submitted 'deactivate node' for worker0.internal.staging.swh.network with UUID ea77128c-eb6f-4370-b018-db88172e4ee1 + puppet node clean worker0.internal.staging.swh.network Notice: Revoked certificate with serial 184 Notice: Removing file Puppet::SSL::Certificate worker0.internal.staging.swh.network at '/var/lib/puppet/ssl/ca/signed/worker0.internal.staging.swh.network.pem' worker0.internal.staging.swh.network + puppet cert clean worker0.internal.staging.swh.network Warning: `puppet cert` is deprecated and will be removed in a future release. (location: /usr/lib/ruby/vendor_ruby/puppet/application.rb:370:in `run') Notice: Revoked certificate with serial 184 + systemctl restart apache2mentioned in commit swh-sysadmin-provisioning@0068053d
mentioned in commit swh/infra/puppet/puppet-swh-site@af48a270
-
terraform:
terraform destroy -target=module.worker0.proxmox_vm_qemu.node module.worker0.proxmox_vm_qemu.node: Refreshing state... [id=pompidou/qemu/117] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: - destroy Terraform will perform the following actions: # module.worker0.proxmox_vm_qemu.node will be destroyed - resource "proxmox_vm_qemu" "node" { - additional_wait = 0 -> null - agent = 0 -> null - args = "-device virtio-rng-pci" -> null - automatic_reboot = true -> null - balloon = 1024 -> null - bios = "seabios" -> null - boot = "c" -> null - bootdisk = "virtio0" -> null - ciuser = "root" -> null - clone = "template-debian-10" -> null - clone_wait = 0 -> null - cores = 2 -> null - cpu = "kvm64" -> null - define_connection_info = true -> null - desc = "Loader/lister service node" -> null - disk_gb = 0 -> null - force_create = false -> null - full_clone = false -> null - guest_agent_ready_timeout = 100 -> null - hotplug = "network,disk,usb" -> null - id = "pompidou/qemu/117" -> null - ipconfig0 = "ip=192.168.130.100/24,gw=192.168.130.1" -> null - kvm = true -> null - memory = 4096 -> null - name = "worker0" -> null - nameserver = "192.168.100.29" -> null - numa = false -> null - onboot = true -> null - oncreate = true -> null - os_type = "cloud-init" -> null - preprovision = true -> null - qemu_os = "other" -> null - reboot_required = false -> null - scsihw = "virtio-scsi-pci" -> null - searchdomain = "internal.staging.swh.network" -> null - sockets = 1 -> null - ssh_host = "192.168.130.100" -> null - ssh_port = "22" -> null - ssh_user = "root" -> null - sshkeys = <<-EOT ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDVKCfpeIMg7GS3Pk03ZAcBWAeDZ+AvWk2k/pPY0z8MJ3YAbqZkRtSK7yaDgJV6Gro7nn/TxdJLo2jEzzWvlC8d8AEzhZPy5Z/qfVVjqBTBM4H5+e+TItAHFfaY5+0WvIahxcfsfaq70MWfpJhszAah3ThJ4mqzYaw+dkr42+a7Gx3Ygpb/m2dpnFnxvXdcuAJYStmHKU5AWGWWM+Fm50/fdMqUfNd8MbKhkJt5ihXQmZWMOt7ls4N8i5NZWnS9YSWow8X/ENOEqCRN9TyRkc+pPS0w9DNi0BCsWvSRJOkyvQ6caEnKWlNoywCmM1AlIQD3k4RUgRWe0vqg/UKPpH3Z root@terraform EOT -> null - tablet = true -> null - target_node = "pompidou" -> null - unused_disk = [] -> null - vcpus = 0 -> null - vlan = -1 -> null - vmid = 117 -> null - disk { - backup = 0 -> null - cache = "none" -> null - file = "vm-117-disk-0" -> null - format = "raw" -> null - iothread = 0 -> null - mbps = 0 -> null - mbps_rd = 0 -> null - mbps_rd_max = 0 -> null - mbps_wr = 0 -> null - mbps_wr_max = 0 -> null - replicate = 0 -> null - size = "32G" -> null - slot = 0 -> null - ssd = 0 -> null - storage = "proxmox" -> null - storage_type = "rbd" -> null - type = "virtio" -> null - volume = "proxmox:vm-117-disk-0" -> null } - network { - bridge = "vmbr443" -> null - firewall = false -> null - link_down = false -> null - macaddr = "72:D9:03:46:B1:47" -> null - model = "virtio" -> null - mtu = 0 -> null - queues = 0 -> null - rate = 0 -> null - tag = -1 -> null } } Plan: 0 to add, 0 to change, 1 to destroy. ╷ │ Warning: Resource targeting is in effect │ │ You are creating a plan with the -target option, which means that the result of this plan may not represent all of the changes requested by the current configuration. │ │ The -target option is not for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or when Terraform specifically │ suggests to use it as part of an error message. ╵ Do you really want to destroy all resources? Terraform will destroy all your managed infrastructure, as shown above. There is no undo. Only 'yes' will be accepted to confirm. Enter a value: yes module.worker0.proxmox_vm_qemu.node: Destroying... [id=pompidou/qemu/117] module.worker0.proxmox_vm_qemu.node: Destruction complete after 6s ╷ │ Warning: Applied changes may be incomplete │ │ The plan was created with the -target option in effect, so some changes requested in the configuration may have been ignored and the output values may not be fully │ updated. Run the following command to verify that no other changes are pending: │ terraform plan │ │ Note that the -target option is not suitable for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or when Terraform │ specifically suggests to use it as part of an error message. ╵ Destroy complete! Resources: 1 destroyed.
Please register or sign in to reply