Bug 1307014

Summary:	Message Running in a container, ignoring fstab device entry does not respect --log-target=null
Product:	[Fedora] Fedora	Reporter:	Jan Pazdziora <jpazdziora>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	johannbg, jpazdziora, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-25 13:40:37 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:

Description Jan Pazdziora 2016-02-12 12:56:19 UTC

Description of problem:

In an attempt to minimize output generated by systemd in dokcer container, I use --log-target=null. However, I still get

Running in a container, ignoring fstab device entry for /dev/disk/by-uuid/06116abf-da19-442c-81f9-543aacaf8f1b.

on docker run (== console) output.

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

$ docker exec systemd rpm -q systemd
systemd-222-10.fc23.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. $ docker run --name systemd -ti -v /run -v /sys/fs/cgroup:/sys/fs/cgroup:ro -e container=docker fedora /usr/sbin/init --show-status=false --log-target=null

Actual results:

Running in a container, ignoring fstab device entry for /dev/disk/by-uuid/06116abf-da19-442c-81f9-543aacaf8f1b.

Expected results:

No output at all.

Additional info:

Note, this is not about the fact that systemd finds record in /etc/fstab which shouldn't be there, that is tracked in https://fedorahosted.org/spin-kickstarts/ticket/54.

Comment 1 Fedora End Of Life 2016-11-24 15:31:50 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Jan Pazdziora 2016-11-25 13:40:37 UTC

I don't see the message printed on Fedora 24 anymore, with neither fedora:23, nor fedora:24 images. Not sure if something got fixed or I'm just not hitting the same situation anymore.

It sure would have been great if someone from the systemd maintainers at least commented on the bugzilla.