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.