Description of problem (please be detailed as possible and provide log
snippests):

The csi pods log message contains the following traces:
2022-07-08T12:26:11.795806762Z I0708 12:26:11.795582 3618438 mount_linux.go:198] Cannot run systemd-run, assuming non-systemd OS
2022-07-08T12:26:11.795806762Z I0708 12:26:11.795599 3618438 mount_linux.go:199] systemd-run output: System has not been booted with systemd as init system (PID 1). Can't operate.
2022-07-08T12:26:11.795806762Z Failed to create bus connection: Host is down
2022-07-08T12:26:11.795806762Z , failed with: exit status 1
2022-07-08T12:26:11.796105554Z I0708 12:26:11.795858 3618438 server.go:131] Listening for connections on address: &net.UnixAddr{Name:"//csi/csi.sock", Net:"unix"}

We noticed that this same issue was solved in upstream:
- https://github.com/ceph/ceph-csi/issues/2890

And there was a recent PR:
- https://github.com/ceph/ceph-csi/pull/3225

Version of all relevant components (if applicable):
- OCS 4.8

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

So far, there is no impact to OCS/ODF features and functions, but this is troublesome because so much log messages are being seeing in the logging stack which could lead to different problems in the future.

Is there any workaround available to the best of your knowledge?

None, that we are aware of.

Can this issue reproducible?

All the time in user environment.



Actual results:

- Lot of messages in CSI pods slowly making a lot of usage in the logging stack

Expected results:

- Reduced logging messages.

Additional info:
- https://github.com/ceph/ceph-csi/issues/64
- https://github.com/ceph/ceph-csi/issues/2890
- https://github.com/ceph/ceph-csi/pull/3225