mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-11-19 04:40:19 +00:00
14ba1498bf
There are regular reports that identify a non-error as the cause of
failures. The Kubernetes mount-utils package has detection for systemd
based environments, and if systemd is unavailable, the following error
is logged:
Cannot run systemd-run, assuming non-systemd OS
systemd-run output: System has not been booted with systemd as init
system (PID 1). Can't operate.
Failed to create bus connection: Host is down, failed with: exit status 1
Because of the `failed` and `exit status 1` error message, users might
assume that the mounting failed. This does not need to be the case. The
container-images that the Ceph-CSI projects provides, do not use
systemd, so the error will get logged with each mount attempt.
By using the newer MountSensitiveWithoutSystemd() function from the
mount-utils package where we can, the number of confusing logs get
reduced.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
|
||
|---|---|---|
| .. | ||
| driver | ||
| clone.go | ||
| controllerserver_test.go | ||
| controllerserver.go | ||
| diskusage.go | ||
| encryption.go | ||
| errors.go | ||
| globals.go | ||
| identityserver.go | ||
| migration_test.go | ||
| migration.go | ||
| mirror.go | ||
| nodeserver_test.go | ||
| nodeserver.go | ||
| rbd_attach_test.go | ||
| rbd_attach.go | ||
| rbd_healer.go | ||
| rbd_journal.go | ||
| rbd_util_test.go | ||
| rbd_util.go | ||
| replicationcontrollerserver_test.go | ||
| replicationcontrollerserver.go | ||
| snapshot.go | ||