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.

> 3. What is the nature and description of the request?  

For having partitions bigger than 2TB, docker-storage-setup would need to be aware of GPT and disk sizes.

> 4. Why does the customer need this? (List the business requirements here)  

Customer manages 8 OCP clusters (regions), some of them, heavily used and currently there's a need to have bigger docker pools. After some experimentation they found the docker-storage-setup doesn't do anything on disks that should use GPT because of their size.

> 5. How would the customer like to achieve this? (List the functional requirements here)  

docker-storage-setup should be aware of disk size and act accordingly, creating GPT table and make use of the available storage.

> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

Configuring a device bigger than 2TB and have docker-storage-setup to configure it properly.

> 10. List any affected packages or components.
docker

Proposed a PR here.

https://github.com/projectatomic/container-storage-setup/pull/266

Franticek can you make sure this updated container-storage-setup gets into the next update of docker for RHEL?

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, 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-2018:2474