Bug 2215142

Summary:	Recovery from failure to run systemctl daemon-reload is many times requires a reinstallation.
Product:	[Fedora] Fedora	Reporter:	Leslie Satenstein <satensteinl>
Component:	syslinux	Assignee:	Peter Jones <pjones>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	39	CC:	fmartine, mattdm, nfrayer, pjones, rharwood, satensteinl
Target Milestone:	---	Keywords:	CodeChange, Desktop, Documentation, SELinux, SupportQuestion
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Leslie Satenstein 2023-06-14 21:43:29 UTC

I do a frequent set of partition reformats as I develop software.
If I fail to run "sudo systemctl daemon-reload", and the reboot is blocked, I have one option.
Format a USB with the Everything.iso and use the recovery option from the Everything.iso grub menu.

The menu will direct the user to the system selected.

That Everything.iso recovery software will set a .autorelabel to root, and hopefully, on reboot, Linux recovery proceeds.  Failure or not, recovery is a VERY LONG PROCEDURE 
Many times, recovery fails (looping). It is then faster and easier to just do a reinstallation. 

 

Reproducible: Sometimes

Steps to Reproduce:
1.  Update /etc/fstab
2.  reboot
3.
Result is system access disabled via SELinux
Actual Results:  
As above


Is there a way, before the user doing a reboot, or when the reboot starts, and the Selinux routine notes that the saved /etc/fstab does not match the updated /etc/fstab,
For the system to prompt to run "sudo systemctl daemon-reload"  BEFORE completing the reboot process.

Recovery should not have to take anywhere from minutes to hours.

My request for filing the bug is for PRODUCT IMPROVEMENT.+

Comment 1 Fedora Release Engineering 2023-08-16 08:11:05 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.