Red Hat Bugzilla – Bug 1289902
Fedora Atomic does not persist journal across reboot
Last modified: 2015-12-10 08:11:25 EST
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
Steps to Reproduce:
$ logger 'BEFORE BOOT'
$ sudo reboot
$ journalctl | grep 'BEFORE BOOT'
Journal is thrown away.
Journal kept past reboot
This bug was caught by the Cockpit integration tests.
I reported this a while back. Would still like for it to be fixed:
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.
(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 ***