
[0;32m[INFO][0m felhom-host-install v1.36.1 — mode=uninstall

[0;34m[STEP][0m UNINSTALL — local host teardown
[0;32m[INFO][0m   no --vmid given; using recorded provisioned_vmid=9201 from /var/lib/felhom-install/state.json
[0;32m[INFO][0m   vmid 9201 looks like a Felhom guest (has the /etc/felhom-bootstrap mount)
[0;32m[INFO][0m   pct config 9201:
    arch: amd64
    cores: 2
    features: nesting=1,keyctl=1
    hookscript: local:snippets/felhom-guest-hook.sh
    hostname: tester4
    memory: 4096
    mp0: local-lvm:vm-9201-disk-1,mp=/var/lib/felhom,backup=1,size=50G
    mp8: /mnt/felhom-drives,mp=/mnt/felhom-drives
    mp9: /var/lib/felhom-agent/guests/9201/bootstrap,mp=/etc/felhom-bootstrap,ro=1
    net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:11:06:5B:AC,ip=dhcp,type=veth
    onboot: 1
    ostype: debian
    rootfs: local-lvm:vm-9201-disk-0,size=32G
    swap: 4096
    unprivileged: 1
Type the vmid (9201) to confirm PERMANENT destruction: 9201
  Logical volume "vm-9201-disk-0" successfully removed.
  Logical volume "vm-9201-disk-1" successfully removed.
[0;32m[OK][0m   guest 9201 destroyed
[0;34m[STEP][0m host-level removal
Removed '/etc/systemd/system/multi-user.target.wants/felhom-agent.service'.
[0;32m[OK][0m   removed /etc/felhom-agent (the agent config and every copy of it)
Removed '/etc/systemd/system/multi-user.target.wants/wg-quick@wg-felhom.service'.
[0;32m[OK][0m   WireGuard tunnel to the Felhom off-site endpoint is down (wg-quick@wg-felhom disabled, conf removed)
Removed '/etc/systemd/system/timers.target.wants/felhom-mgmt-watchdog.timer'.
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
Removed '/etc/systemd/system/pve-guests.service.wants/felhom-shared-parent.service'.
Removed '/etc/systemd/system/multi-user.target.wants/felhom-shared-parent.service'.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-7.0.2-6-pve
Found initrd image: /boot/initrd.img-7.0.2-6-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Adding boot menu entry for UEFI Firmware Settings ...
done
[0;36m[SKIP][0m   old broad role FelhomAgent already absent
[0;36m[SKIP][0m   golden vzdump left in place (pass --remove-golden to remove)

[0;34m[STEP][0m kept vs wiped — read before pulling drives or closing the customer out
  WIPED (this run):
    - guest 9201 (container + its OS/Docker/user-data volumes)
    - the felhom-agent: binary, unit, sudoers (+ its copies), state dir, service user, and its config
      directory with every copy of the config in it
    - the WireGuard tunnel to the Felhom off-site endpoint (wg-quick@wg-felhom disabled, /etc/wireguard/wg-felhom.conf removed)
    - self-update artifacts: guarded wrapper, A/B slots (.prev/.new.*), rollback unit, start-limit drop-in
    - break-glass watchdog + OOB artifacts (where present); guest-hook snippet; dnsmasq snippets; the mkfs, pbs-apply,
      backup-target-apply, os-apply and priv-apply wrappers; the crash guard; the config-bundle record
    - pveum: the Felhom roles/user/token/scoped ACL; the emptied felhom pool
    - the install state file
  KEPT (lives on deliberately — remove/rotate these out-of-band if the customer is leaving):
    - the enrolled drives + ALL data under /mnt/felhom-drives — unmounted only, NEVER wiped;
      the drives are physically removable now.
    - the PBS backups + this customer's namespace on the PBS side — delete there if wanted
    - the hub host/customer record + report history (operator UI / DB)
    - this host's WireGuard PEER on the hub and the off-site endpoint (its /32 and public key) — the
      tunnel is down from this side; delete the peer in the hub (operator) if the customer is leaving
    - the escrow blob in the hub, if one exists (operator UI)

[0;32m[OK][0m UNINSTALL complete — removed: guest 9201, the felhom-agent (unit/sudoers/binary/state/config+baks/user + selfupdate-artifacts/shared-parent/mkfs-wrapper/pbs-apply-wrapper/hook-snippet/dnsmasq-snippets), the pveum role/user/token/ACL, the felhom pool, and /var/lib/felhom-install/state.json.
[0;32m[INFO][0m   golden vzdump: left in place (--remove-golden to remove).
[0;32m[INFO][0m   NOTE: the 'sudo' package was left INSTALLED (a system package, never ours to remove). dnsmasq is removed only when the install-time record says Felhom installed it; a resolver that pre-dated Felhom is never touched. The host record still exists in the hub — remove it there if desired.
UNINSTALL_RC=0
Connection to 192.168.0.127 closed.
