Bug 1011706

Summary:	RFE: systemd should never drop to recovery console without explaining why
Product:	[Fedora] Fedora	Reporter:	Nicolas Mailhot <nicolas.mailhot>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dominik, dtardon, johannbg, lnykryn, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
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:	2022-09-13 08:50:27 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:

Description Nicolas Mailhot 2013-09-24 21:40:20 UTC

right now systemd will happily drop people to the recovery console without explianing why and telling them to go dig in journalctl for the reason themselves

Also the boot can fail but systemctl pretend no service failed

Systemd should plainly exply what condition caused it to drop to the recovery console, it should extract the relevant parts of the log itself (what's the point of the journal if systemd can not even log its own actions properly), and systemctl should not pretend all is fine when systemd just triggered the recovery mode

systemd-207-4

Comment 1 David Tardon 2022-09-13 08:50:27 UTC

Fedora is not the place where systemd development is happening. Please report your enhancement request to https://github.com/systemd/systemd/issues . Thank you for understanding.