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.

Filed from caserun https://tcms.engineering.redhat.com/run/302817/?#caserun_14993827

Version-Release number of selected component (if applicable):
observed with both
util-linux-2.23.2-33.el7
util-linux-2.23.2-33.el7_3.1

Steps to Reproduce: 
run /CoreOS/util-linux/Regression/bz1208081-RHEL7-lsblk-does-not-list-dm-multipath-and

Actual results: 
NAME        MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda           8:0    0  500M  0 disk  
└─mpatha    253:2    0  500M  0 mpath 
  └─mpatha1 253:3    0  499M  0 part  


Expected results:
NAME                MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda                   8:0    0  500M  0 disk  
├─sda1                8:1    0  500M  0 part  
└─mpatha (dm-0)     253:0    0  500M  0 mpath 
  └─mpathap1 (dm-1) 253:1    0  500M  0 part

ahem, sorry to intervene when I no longer maintain the test, however, in the original bug 1208081 it was specifically requested to show the partition, so a 'solution' like "we don't show it anymore by default, let's include a workaround in the test that will get the output back" just doesn't seem right to me

... but maybe I got the above conversation wrong, apologies then

It's not that we simply don't show the partition device; we actually remove it. So /dev/sda1 doesn't exist if /dev/sda is used by multipath, unless the user runs partprobe to bring it back.  Thus, the lsblk behavior seems correct, and we aren't changing the multipath behavior, because doing so would bring back all the customer issues that caused us to change it in the first place. This was previously only done by multipath in RHEL, but it is now upstream.

Unless anyone has any objections, I'm going to close this NOTABUG