Description of problem: In OCS 3.11.4 container, there are 2 services failing which also causes journalctl not to work at all. [root@master1 ~]# oc rsh glusterfs-registry-q4xhj sh-4.2# systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● systemd-journal-flush.service loaded failed failed Flush Journal to Persistent Storage ● rpcbind.socket loaded failed failed RPCbind Server Activation Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 2 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. Version-Release number of selected component (if applicable): v3.11.4
Is that reproducible, still happening with latest bits?
(In reply to Yaniv Kaul from comment #2) > Is that reproducible, still happening with latest bits? Yes, it is still reproducible with latest bits. However, there is no functional impact other than debugging being less intuitive as journalctl command does not show logs. Log files can still be seen in usual location. We will fix this in next release.
Changing the scope of the bug. We cannot enable journalctl in the container because we have turned down other required services. However, we should make it so that there are no failed services in the containers. Hence, we should mask the following two services systemd-journal-flush.service rpcbind.socket
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0622