Bug 1319870

Summary:	udevadm info fails to display some partition devices when specified by name
Product:	Red Hat Enterprise Linux 7	Reporter:	mulhern <amulhern>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	harald, systemd-maint-list, udev-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:40:35 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 mulhern 2016-03-21 17:41:38 UTC

Description of problem:

Specifying partition device by name causes lookup failure, even though
udevadm info reports on the device using export-db

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

[root@megadeth pydevDAG]# udevadm --version
219

How reproducible:

Always.

Steps to Reproduce:
1.

[mulhern-journal@megadeth pydevDAG]$ udevadm info --export-db | grep sde1
P: /devices/pci0000:00/0000:00:01.0/0000:09:00.0/host0/port-0:0/expander-0:0/port-0:0:3/end_device-0:0:3/target0:0:2/0:0:2:0/block/sde/sde1
N: sde1
E: DEVNAME=/dev/sde1
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:09:00.0/host0/port-0:0/expander-0:0/port-0:0:3/end_device-0:0:3/target0:0:2/0:0:2:0/block/sde/sde1

sde1 in database, clearly.

2.

[mulhern-journal@megadeth pydevDAG]$ udevadm info /dev/sde1
Unknown device, --name=, --path=, or absolute path in /dev/ or /sys expected.


[mulhern-journal@megadeth pydevDAG]$ udevadm info -name=sde1
device node not found

3.

[mulhern-journal@megadeth pydevDAG]$ ls /dev/sde1
/dev/sde1

udevadm info /sys/devices/pci0000:00/0000:00:01.0/0000:09:00.0/host0/port-0:0/expander-0:0/port-0:0:3/end_device-0:0:3/target0:0:2/0:0:2:0/block/sde/sde1
works

Actual results:

Partition device not found when specified by name or device node although available in database.

Expected results:

All ways of specifying the device should work.

Additional info:

This may have to do with the fact that the partition device seems somewhat to be a character device: see bz#1319853.

Comment 2 Harald Hoyer 2016-04-04 09:40:43 UTC

Why on earth is sde1 a character device? Which application created the device node?

Comment 3 mulhern 2016-04-04 12:30:50 UTC

Comment #2: It became a character device when I rebooted, without any action on my part. The reason is still unknown: bz#1319819.

Comment 6 RHEL Program Management 2020-12-15 07:40:35 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.