search

piraeusdatastore / drbd-shutdown-guard

Aid Kubernetes cluster using DRBD® with `suspend-io` behaviour during shutdown
0 stars 0 forks source link

failed to reload systemd #8

Open DeanKamali opened 3 weeks ago

DeanKamali commented 3 weeks ago

on fresh / vanilla install, I get this error

kubectl apply --server-side -k "https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.6.0"

drbd-shutdown-guard seem to always have an issue reloading the systemd 

kubectl logs -n piraeus-datastore linstor-satellite.node1-xhvpp -c drbd-shutdown-guard
2024/10/29 14:48:20 Running drbd-shutdown-guard version v1.0.0
2024/10/29 14:48:20 Creating service directory '/run/drbd-shutdown-guard'
2024/10/29 14:48:20 Copying drbdsetup to service directory
2024/10/29 14:48:20 Copying drbd-shutdown-guard to service directory
2024/10/29 14:48:20 Optionally: relabel service directory for SELinux
2024/10/29 14:48:20 ignoring error when setting selinux label: exit status 127
2024/10/29 14:48:20 Creating systemd unit drbd-shutdown-guard.service in /run/systemd/system
2024/10/29 14:48:20 Reloading systemd
Error: failed to reload systemd
Usage:
  drbd-shutdown-guard install [flags]

Flags:
  -h, --help   help for install

2024/10/29 14:48:20 failed: failed to reload systemd

My k8s node (k3s) 

 cat /etc/issue
Ubuntu 22.04.5 LTS \n \l
WanzenBug commented 3 weeks ago

There is already some discussion going on at https://github.com/piraeusdatastore/piraeus-operator/issues/426

My best guess is currently that k3s does not actually mount through the right host directory.