RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1319870 - udevadm info fails to display some partition devices when specified by name
Summary: udevadm info fails to display some partition devices when specified by name
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 17:41 UTC by mulhern
Modified: 2020-12-15 07:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:40:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1319819 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1319853 0 unspecified CLOSED -c option exits with 'requires a path to check' error, but path is there 2021-09-03 11:57:52 UTC

Internal Links: 1319819 1319853

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.
Note You need to log in before you can comment on or make changes to this bug.