Bug 1748420

Summary:	systemd units rpcbind.socket and systemd-journal-flush.service show status failed
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra Talur <rtalur>
Component:	rhgs-server-container	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED ERRATA	QA Contact:	Arun Kumar <arukumar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	arukumar, jmulligan, kramdoss, madam, puebele, rhs-bugs, ykaul
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhgs-server-container-3.11.5-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-26 20:25:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raghavendra Talur 2019-09-03 14:34:37 UTC

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

Comment 2 Yaniv Kaul 2019-09-15 12:52:32 UTC

Is that reproducible, still happening with latest bits?

Comment 3 Raghavendra Talur 2019-09-16 02:59:29 UTC

(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.

Comment 4 Raghavendra Talur 2019-11-11 19:59:45 UTC

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

Comment 12 errata-xmlrpc 2020-02-26 20:25:33 UTC

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