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.

Description of problem:
Deploying compute nodes with 10TB disk which they want to use entirely for the OS because all the VM's will be using the ephermal disk.
Somehow, we found growpart failed to extend the disk.
System set only 2tb partition.
Looking at RHEL8 cloud-init-growpart package that RHBA-2019:1900 was not ported.
Related BZ: 1726564
KCS: https://access.redhat.com/solutions/4350511
Similar case: https://access.redhat.com/support/cases/#/case/02414337

Version-Release number of selected component (if applicable):
RHOSP 16.1
RHEL 8.2

How reproducible:


Steps to Reproduce:
1. Deploy compute node trying to assign more than 2 TB to local storage
2.
3.

Actual results:
2 TB partition for compute node

Expected results:
10 TB partition

Additional info:

Trying to link current case from Salesforce but I can't: https://gss--c.visualforce.com/apex/Case_View?id=5002K00000v07wi

Hello.

I would like to provide extra perspective for this bug to justify a fix: it is important to understand impact since RHEL 8.2 is in EUS stage.

cloud-utils-growpart is used by RHOSP itself when overcloud nodes (Controllers, Computes, Ceph nodes, etc) are added to overcloud during initial deployment or scale-out procedures. Red Hat OpenStack 16.1 is only supported with Red Hat Enterprise Linux 8.2. Red Hat will not support Red Hat Openstack 16.1 with Red Hat Enterprise Linux 8.2 after April 30, 2024. [1]

As a result, from RHOSP perspective this bug is a blocker for some customers that use RHOSP 16.1 product and could still use it for ~3 years. So this is not only about customer running RHEL 8.2 with huge disks in the cloud (rare situation), but also about RHOSP 16.1 customers with relatively huge disk drives on their overcloud nodes.

Hope that this message would help to prioritize this properly.

[1]
https://access.redhat.com/support/policy/updates/openstack/platform

Regards, Alex.

ACK on the summary.

Merge request is up https://gitlab.com/redhat/rhel/src/cloud-utils/-/merge_requests/2