Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Created attachment 489329 [details]
udevadm full output

Description of problem:
udevadm can not handle cciss driver's device file without full path

Version-Release number of selected component (if applicable):
udev-147-2.29.el6.i686

How reproducible:
Always 

Steps to Reproduce:
If you want to reproduce this symptom,
you need to use a system with SmartArray (cciss) is installed.

Bad examples
# udevadm info --query=all --name=c0d0
device node not found

# udevadm info --query=all --name=c0d0p1
device node not found

Good example (See attached file for full output)
# udevadm info --query=all --name=/dev/cciss/c0d0
P: /devices/pci0000:40/0000:40:11.0/0000:48:00.0/cciss0/c0d0/block/cciss!c0d0
N: cciss/c0d0
W: 37
S: block/104:0
S: disk/by-id/cciss-3600508b100105039565759303555002a
S: disk/by-path/pci-0000:48:00.0
S: disk/by-id/wwn-0x600508b100105039565759303555002a
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:40/0000:40:11.0/0000:48:00.0/cciss0/c0d0/block/cciss!c0d0
E: MAJOR=104
E: MINOR=0
E: DEVNAME=/dev/cciss/c0d0
E: DEVTYPE=disk
E: SUBSYSTEM=block
E: ID_SCSI=1
E: ID_VENDOR=HP
E: ID_VENDOR_ENC=HP\x20\x20\x20\x20\x20\x20
E: ID_MODEL=LOGICAL_VOLUME
E: ID_MODEL_ENC=LOGICAL\x20VOLUME\x20\x20
E: ID_REVISION=7.22
E: ID_TYPE=disk
(snip)

what's the output of:
# udevadm info --query=all --name=cciss/c0d0

(In reply to comment #0)
> Good example (See attached file for full output)
> # udevadm info --query=all --name=/dev/cciss/c0d0
> N: cciss/c0d0

Here you see the name... "cciss/c0d0" !

For example,  if it is a scsi device,  both sda and /dev/sda returns same
result.

But in cciss case, c0d0 returns "device node not found",
and /dev/cciss/c0d0 returns correct result.
I thought udevadm can not handle cciss case, because cciss driver have 
one more path depth than other devices.

Confirmed  -name=cciss/c0d0 works.
Thanks.

If you think this is not a bug, would you agree to modify the man page?

Current:
--name=file
    The name of the device node or a symlink to query 

Proposed:
--name=file
    The name of the device node specified by a path from /dev or a symlink to query.