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 2064176

Summary: gdisk naming partitions doesn't work for big endian systems
Product: Red Hat Enterprise Linux 8 Reporter: Martin Kyral <mkyral>
Component: gdiskAssignee: Nikola Forró <nforro>
Status: CLOSED DUPLICATE QA Contact: Martin Kyral <mkyral>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.6Keywords: Regression
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: s390x   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-18 10:10:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Kyral 2022-03-15 08:36:59 UTC
Description of problem:

On s390x systems, when we print partition names in gdisk, they are broken:


[root@s390x-kvm-039 ~]# gdisk -l /tmp/tmp.ydqTCA2yF4
GPT fdisk (gdisk) version 1.0.3

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /tmp/tmp.ydqTCA2yF4: 131072 sectors, 64.0 MiB
Sector size (logical): 512 bytes
Disk identifier (GUID): DFB1F964-24E7-412D-9A25-7837EB2D29A5
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 131038
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          131038   63.0 MiB    8300  䰀椀渀甀砀 昀椀氀攀猀礀猀琀攀洀
[root@s390x-kvm-039 ~]# 


while it should be like:

[root@ibm-z-532 ~]# gdisk -l /tmp/tmp.trTgCQifmd
GPT fdisk (gdisk) version 1.0.3

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /tmp/tmp.trTgCQifmd: 131072 sectors, 64.0 MiB
Sector size (logical): 512 bytes
Disk identifier (GUID): F067F1C3-740C-4D38-839A-42872727BA64
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 131038
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          131038   63.0 MiB    8300  Linux filesystem
[root@ibm-z-532 ~]# 

it seems the bytes order is reversed. The issue has been apparently introduced by fix for BZ#1899990.


Version-Release number of selected component (if applicable):

gdisk-1.0.3-8.el8


How reproducible:
Always


Steps to Reproduce:
1. run the /usr/share/doc/gdisk/gdisk_test.sh script. Make sure it runs on installed gdisk
2.
3.

Actual results:
Fails in the second step:

**FAILED** Create new partition


Expected results:

All pass


Additional info: