Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1811155

Summary:	/dev/disk/by-uuid not populated for mdraid devices
Product:	[Fedora] Fedora	Reporter:	Alexis Jeandet <alexis.jeandet>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	32	CC:	lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-07 09:25:58 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 Alexis Jeandet 2020-03-06 18:02:29 UTC

Description of problem:
After upgrading my computer from fc31 to fc32 /dev/disk/by-uuid doesn't contain anymore mdraid devices.

Version-Release number of selected component (if applicable):

Name         : systemd-udev
Version      : 245~rc1
Release      : 4.fc32
Architecture : x86_64
Size         : 8.3 M
Source       : systemd-245~rc1-4.fc32.src.rpm
Repository   : @System
From repo    : updates-testing


How reproducible:
Since upgrade (last week), on each update+reboot the problem is still there.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

I've no idea what to look/test to give more helpful info. Feel free to ask me anything to test.

Comment 1 Alexis Jeandet 2020-03-06 18:08:57 UTC

Seems related to https://bugzilla.redhat.com/show_bug.cgi?id=1809117

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-03-07 09:25:58 UTC

This is almost certainly caused by #1809117. If the issue is not fixed, please reopen.

*** This bug has been marked as a duplicate of bug 1809117 ***