Bug 1254874

Summary:	Boot fails with SIGRTMIN+21 from plymoutd
Product:	Red Hat Enterprise Linux 7	Reporter:	Robin Hack <rhack>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	systemd-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-26 10:29:34 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:
Embargoed:

Description Robin Hack 2015-08-19 07:28:42 UTC

Description of problem:
Hi. I upgraded my testing rhel 7.2 system as usual and I got unbootable system.

Only what I have is rescue shell.


Version-Release number of selected component (if applicable):
systemd-219-11/el7.x86_64

How reproducible:
always (for me)

Steps to Reproduce:
1. I don't know. I upgraded my rhel7.2 machine.

Actual results:
unbootable system

From journald:
Received SIGRTMIN+21 from PID 255 (plymouthd).

(as a side efect.. abrt-cli dies in pain with SIGSEGV.. ha ha).

Expected results:
Warm toasts ... I'm not able to boot my toaster!

Additional info:

Comment 4 Robin Hack 2015-08-26 10:29:34 UTC

I found that some automatization added cripled records to /etc/fstab.