Bug 888618

Summary: /var/lib/random-seed file is not functional under readonly root enabled
Product: [Fedora] Fedora Reporter: Joey Boggs <jboggs>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: dsd, huli, iarlyy, johannbg, jonathan, lnykryn, metherid, notting, plautrba, rvokal, systemd-maint, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 808907 Environment:
Last Closed: 2013-03-13 09:55:17 UTC Type: ---
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: 808907    
Bug Blocks:    

Description Joey Boggs 2012-12-19 02:32:34 UTC 
+++ This bug was initially created as a clone of Bug #808907 +++

Description of problem:
/var/lib/random-seed file is not functional under readonly root enabled. This file cannot be removed due to "Read-only file system" error and the system will show the error message when booting: "systemd-random-seed[517]: Failed to write new random seed file: Bad file descriptor".

Version-Release number of selected component (if applicable):
initscripts-9.34.2-1.fc16.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Just install base and core groups
2. Enable readonly root function in /etc/sysconfig/readonly-root file, set READONLY=yes and TEMPORARY_STATE=yes.
3. Add mount option ro in /etc/fstab for / directory.
4. Reboot
  
Actual results:
"systemd-random-seed[517]: Failed to write new random seed file: Bad file descriptor" and the file cannot be removed/modified.

Expected results:
No error for /var/lib/random-seed.


Seeing the same error in Fedora 18 alpha still.
Comment 1 Lukáš Nykrýn 2013-03-13 09:55:17 UTC 

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