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.

Bug 2180782

Summary: mkfs.gfs2: backport -U UUID option to RHEL 8.9
Product: Red Hat Enterprise Linux 8 Reporter: Andrew Price <anprice>
Component: gfs2-utilsAssignee: Andrew Price <anprice>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact: Steven J. Levine <slevine>
Priority: medium    
Version: ---CC: cluster-maint, gfs2-maint, slevine
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gfs2-utils-3.2.0-13.el8 Doc Type: Enhancement
Doc Text:
.Support for specifying a UUID when creating a GFS2 file system The `mkfs.gfs2` command now supports the new `-U` option, which makes it possible to specify the file system UUID for the file system you create. If you omit this option, the file system’s UUID is generated randomly.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-14 15:47:29 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Price 2023-03-22 09:27:11 UTC
Upstream mkfs.gfs2 has a new -U option for specifying the UUID, which will be useful in the gfs2 Ansible role. mkfs.gfs2 is also one of only a few mkfses that doesn't have a UUID option, so this will give it a more complete feature set.

There should only be one small upstream patch to backport: https://pagure.io/gfs2-utils/c/822f230e3f60a9643c6bb4d90c48c57207ba371c.patch

Comment 5 Andrew Price 2023-05-23 10:27:34 UTC
Testing notes: The test suite that runs at package build time contains some basic validation tests: https://pagure.io/gfs2-utils/blob/RHEL8/f/tests/mkfs.at#_178-182

Beyond that, some additional tests could be:

uuid=$(uuidgen)
mkfs.gfs2 -U $uuid ... $device
mount $device $mountpoint
grep -Hi $uuid /sys/fs/gfs2/$(basename $(readlink -f $device))`/uuid
umount $device
tunegfs2 -l $device | grep $uuid

Comment 12 Nate Straz 2023-08-09 18:53:53 UTC
Verified with some manual testing with gfs2-utils-3.2.0-13.el8.x86_64

Comment 16 errata-xmlrpc 2023-11-14 15:47:29 UTC
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 (gfs2-utils 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-2023:7086