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.
DescriptionIrving Popovetsky
2014-10-22 18:09:26 UTC
Description of problem:
RHEL AMIs should be able to be launched with a larger root volume, and they should automatically resize the root volume to fill the available space using cloud-init and growpart.
This has worked well with the RHEL 6.5 PV AMIs, but no longer works with RHEL 6 HVM and RHEL 7 HVM AMIs which now use GPT-partitioned root volumes.
Version-Release number of selected component (if applicable):
cloud-init 0.7.5
How reproducible: 100% reproducible
Steps to Reproduce:
1. In the EC2 console, select an AMI based on the RHEL-6.5_GA_HVM-20140929-x86_64-11-Hourly2-GP2, RHEL-6.6_HVM_GA-20141017-x86_64-1-Hourly2-GP2 or RHEL-7.0_HVM_GA-20141017-x86_64-1-Hourly2-GP2
2. Select a larger than default root volume size (ex: 10 GB)
3. Launch it
Actual results:
Root volume remains 5.8 GB
/var/log/cloud-init.log says:
Oct 21 18:14:09 ip-rhel-backend2 cloud-init: 2014-10-21 18:14:09,664 - util.py[WARNING]: Failed: growpart /dev/xvda 2
A reboot is required for the partition table to be re-read:
[root@ip-33-33-33-96 ~]# growpart /dev/xvda 2
failed [pt_update:1] pt_update /dev/xvda 2
partx: /dev/xvda: error updating partition 2
FAILED: disk=/dev/xvda partition=2: failed to repartition
***** WARNING: Resize failed, attempting to revert ******
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
***** Appears to have gone OK ****
[root@ip-33-33-33-96 ~]# growpart -u off /dev/xvda 2
CHANGED: disk=/dev/xvda partition=2: start=4096 old: size=12582911,end=12587007 new: size=25161694,end=25165790
[root@ip-33-33-33-96 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 12G 0 disk
├─xvda1 202:1 0 1M 0 part
└─xvda2 202:2 0 6G 0 part /
xvdb 202:16 0 37.5G 0 disk /mnt
[root@ip-33-33-33-96 ~]# partx -v --update 2 /dev/xvda
partition: 2, disk: /dev/xvda, lower: 2, upper: 2
/dev/xvda: partition table type 'gpt' detected
partx: /dev/xvda: updating partition #2 failed: Device or resource busy
partx: /dev/xvda: error updating partition 2
Expected results:
root volume resizes to 10GB automatically on boot
Additional info:
1. the gdisk package is not installed, so growpart
2. RHEL6 partx command doesn't support the -u (--update) option
3. RHEL7 partx does support the -u option, but it always fails with a "device or resource busy"
Closing in favor of Bug #1162228 which contains situation analysis and depends on already identified issues.
For RHEL6.x GPT amis please refer to Bug #1110029
*** This bug has been marked as a duplicate of bug 1162228 ***