Bug 1888730

Summary:	Booting with a RAID attached results in mdmonitor failing to start
Product:	[Fedora] Fedora	Reporter:	Brian Lane <bcl>
Component:	lorax	Assignee:	Brian Lane <bcl>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	32	CC:	anaconda-maint-list, bcl, jwboyer, reallylongword, release-test-team-automation
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	lorax-34.4-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1888728	Environment:
Last Closed:	2021-03-01 19:33:03 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:
Bug Depends On:	1888728
Bug Blocks:

Description Brian Lane 2020-10-15 15:38:02 UTC

+++ This bug was initially created as a clone of Bug #1888728 +++

The mdmonitor service is disabled on the installer iso, but if there is a RAID attached systemd tries to start it anyway. This results in an error in the logs and on the console.

The system continues to boot, and installation works fine, this is purely cosmetic.

It does not appear with a normally partitioned drive, only with RAID.

We do not want to actually run mdmonitor during installation because it requires an email address to function properly. So it either needs to be removed or masked from being started under any conditions.

Comment 1 Brian Lane 2020-10-30 19:22:17 UTC

https://github.com/weldr/lorax/pull/1092