We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
The text was updated successfully, but these errors were encountered:
There is already some discussion going on at piraeusdatastore/piraeus-operator#426
My best guess is currently that k3s does not actually mount through the right host directory.
Sorry, something went wrong.
No branches or pull requests
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
My k8s node (k3s)
The text was updated successfully, but these errors were encountered: