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.

+++ This bug was initially created as a clone of Bug #2078815 +++

libblockdev uses `mdadm --examine` which doesn't contain UUID for RAID containers (like DDF or IMSM. We need to get it from `mdadm --examine --brief` instead.

upstream issue: https://github.com/storaged-project/libblockdev/issues/722

--- Additional comment from guazhang on 2022-04-26 09:56:32 UTC ---

Hi,

Did the libblockdev case cover it ?

--- Additional comment from Vojtech Trefny on 2022-04-27 09:06:36 UTC ---

(In reply to guazhang from comment #1)
> Hi,
> 
> Did the libblockdev case cover it ?

No, this currently isn't covered by the libblockdev test suite. I'll try to add a test case for it, but we might need a special hardware to test this (creating a fake/emulated DDF array might be possible for the test). I'll let you know when I have a patch ready.

upstream PR: https://github.com/storaged-project/libblockdev/pull/563 and https://github.com/storaged-project/libblockdev/pull/762

Tests are part of the second PR. For manual testing:

1. Create the DDF RAID with mdadm

# mdadm --create /dev/md/ddf --name=ddf --level container --raid-disks=2 --metadata=ddf /dev/vda /dev/vdb
# mdadm --create /dev/md/vol0 --name=vol0 --level raid1 --raid-disks=2 /dev/md/ddf

2. Check that libblockdev can get UUID of the container both with `bd_md_examine` and `bd_md_detail`:

In [2]: examine_data = BlockDev.md_examine("/dev/vda")
In [3]: examine_data.uuid
Out[3]: '50efb57b-85be-0a7e-47f6-6b7ff6b47e63'

In [4]: detail_data = BlockDev.md_detail("/dev/md/ddf")
In [5]: detail_data.uuid
Out[5]: '50efb57b-85be-0a7e-47f6-6b7ff6b47e63'

*** Bug 2079359 has been marked as a duplicate of this bug. ***

test pass with fix package, move to verified

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (libblockdev bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8118