Bug 1482460

Summary: [AWS][EC2]The system disk partition type displays as "Microsoft basic data" in RHEL guests on EC2
Product: Red Hat Enterprise Linux 7 Reporter: Lin Liu <linl>
Component: ec2-imagesAssignee: Jon Disnard <jdisnard>
Status: CLOSED ERRATA QA Contact: Lin Liu <linl>
Severity: high Docs Contact:
Priority: high    
Version: 7.4CC: cheshi, jgreguske, leiwang, linl, salmy, wshi, xiliang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 11:41:59 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:

Description Lin Liu 2017-08-17 10:39:51 UTC
Description of problem:

The system disk partition type displays as "Microsoft basic data" in RHEL guests on EC2.

[root@ip-172-31-8-133 ~]# fdisk -l
#         Start          End    Size  Type            Name
 1         2048         4095      1M  BIOS boot parti
 2         4096     41943006     20G  Microsoft basic

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

How reproducible:

Steps to Reproduce:

1. Start a RHEL7.4 instance on EC2.
2. Connect the instance and check the partition type of the system disk with "sudo fdisk -l" command.

Actual results:
The Partition type is "Microsoft basic data" as default.

Expected results:
The Partition type should be "Linux filesystem".

Additional info:
1. The default partition type is "Microsoft basic data" if using "parted" command to manipulate disk partitions.
   We can see from the ks file "original-ks.cfg" in the instance that we use parted command during building the image, so please change the partition type after manipulating disk partitions or using fdisk to make the partitions.
2. I checked Amazon Linux, the partition type is "Linux filesystem".

Comment 10 errata-xmlrpc 2019-08-06 11:41:59 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, and where to find the updated
files, follow the link below.

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