Bug 1649630

Summary:	tcmu-runner/dyn-logger: DEBUG SCSI CMD loglevel is not working in the container which has no syslogd service installed
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Xiubo Li <xiubli>
Component:	tcmu-runner	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED ERRATA	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	akrishna, bgoyal, knarra, kramdoss, nberry, pkarampu, prasanna.kalever, rhs-bugs, sankarshan, vbellur, xiubli
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tcmu-runner-1.2.0-28.el7rhgs	Doc Type:	Bug Fix
Doc Text:	Previously, the DEBUG_SCSI command logs from tcmu-runner daemon were dumped to stdout, which were expected to be recorded by the syslog buffer. Currently, this is not working as expected as most containers are not running syslogd service. With this fix, the DEBUG_SCSI command logs are pushed through syslog system call. Hence, the container host node will record the logs in the absence of syslogd service inside the container.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-07 03:38:29 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:
Bug Depends On:
Bug Blocks:	1641915, 1644160

Description Xiubo Li 2018-11-14 06:07:32 UTC

Description of problem:

Currently the DEBUG SCSI CMD loglevel logs are all outputed to the stdout file, which will record to the syslogd buffer, but mostly the container pod won't install the syslogd service, so will miss the DEBUG SCSI CMD logs here.

Why we didn't record this logs to tcmu-runner.log file was because this logs will burst and quickly run out of the disk space if running for a long time without the logrotate support.

In the upstream the log rotate feature has been supported and change it back to tcmu-runner.log.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Prasanna Kumar Kalever 2018-11-14 06:17:36 UTC

PR: https://github.com/open-iscsi/tcmu-runner/pull/480

Comment 13 errata-xmlrpc 2019-02-07 03:38:29 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-2019:0285