Bug 1289902

Summary:	Fedora Atomic does not persist journal across reboot
Product:	[Fedora] Fedora	Reporter:	Stef Walter <stefw>
Component:	atomic	Assignee:	Colin Walters <walters>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	adimania, dperpeet, dustymabe, dwalsh, lsm5, mvollmer, walters
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:	2015-12-10 13:11:25 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 Stef Walter 2015-12-09 10:17:54 UTC

Description of problem:

Fedora Atomic (unlike Fedora) does not persist its journal across reboots. This means that all the new work centering around the journal (such as the docker's journal driver, and cockpit's journal inspector) are far less useful on Fedora Atomic.

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

* 2015-12-08 21:17:20     22.185             82212b2ac6     fedora-atomic     fedora-atomic:fedora-atomic/f22/x86_64/docker-host     


How reproducible:

Every time

Steps to Reproduce:
$ logger 'BEFORE BOOT'
$ sudo reboot
$ journalctl | grep 'BEFORE BOOT'

Actual results:

Journal is thrown away.

Expected results:

Journal kept past reboot

Comment 1 Stef Walter 2015-12-09 10:18:17 UTC

This bug was caught by the Cockpit integration tests.

Comment 2 Dusty Mabe 2015-12-09 13:55:38 UTC

I reported this a while back. Would still like for it to be fixed:

https://bugzilla.redhat.com/show_bug.cgi?id=1265295

Comment 3 Dusty Mabe 2015-12-09 15:36:25 UTC

Stef, can you confirm it is the same bug? After the 2nd reboot is the journal persisted to disk?

Colin, what component should this bug be under? I opened 1265295 against rpm-ostree.

Comment 4 Stef Walter 2015-12-10 13:11:25 UTC

(In reply to Dusty Mabe from comment #2)
> I reported this a while back. Would still like for it to be fixed:

OSTree instances are brought up (eg: in the cloud) and not necessarily rebooted before use would be affected by this. So it's not a corner case.

(In reply to Dusty Mabe from comment #3)
> Stef, can you confirm it is the same bug? After the 2nd reboot is the
> journal persisted to disk?

It is the same bug. Will mark this as a duplicate.

*** This bug has been marked as a duplicate of bug 1265295 ***