Bug 1387796

Summary:	RFE: switch to persistent journal by default, don't autodetect from /var
Product:	[Fedora] Fedora	Reporter:	Colin Walters <walters>
Component:	systemd	Assignee:	systemd-maint
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dtardon, johannbg, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Colin Walters 2016-10-21 22:40:46 UTC

Autodetecting whether or not to persist the journal from the presence of /var/log/journal conflicts with the "factory reset" logic as implemented by ostree (/var/ starts out empty).

We're currently carrying
https://pagure.io/fedora-atomic/blob/37389c874240db4055c8076600a89a5fa3eba4a7/f/treecompose-post.sh#_6
and while this one-liner is not a huge burden, I'm trying to track our downstream workarounds and continually approach the ideal of having the base RPMs work without tweaking.

My suggestion here is an upstream flag like --enable-journal-storage-default=persistent that we set in the spec.

Comment 1 Zbigniew Jędrzejewski-Szmek 2017-01-18 19:01:53 UTC

Yeah, I think the time has come to do something like this. I think we might event want to do this upstream.