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
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.