mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-12-19 03:20:20 +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>
|
||
|---|---|---|
| .. | ||
| k8s | ||
| log | ||
| reftracker | ||
| cephcmds_test.go | ||
| cephcmds.go | ||
| cephconf.go | ||
| cluster_mapping_test.go | ||
| cluster_mapping.go | ||
| conn_pool_test.go | ||
| conn_pool.go | ||
| connection.go | ||
| credentials_test.go | ||
| credentials.go | ||
| crypto_test.go | ||
| crypto.go | ||
| cryptsetup.go | ||
| csiconfig_test.go | ||
| csiconfig.go | ||
| errors_test.go | ||
| errors.go | ||
| httpserver.go | ||
| idlocker_test.go | ||
| idlocker.go | ||
| pidlimit_test.go | ||
| pidlimit.go | ||
| stripsecrets.go | ||
| topology_test.go | ||
| topology.go | ||
| util_test.go | ||
| util.go | ||
| validate.go | ||
| volid_test.go | ||
| volid.go | ||