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 1272253 - EC2 Root partition does not get resized to the available space after updates are applied
Summary: EC2 Root partition does not get resized to the available space after updates ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ec2-images
Version: 6.7
Hardware: All
OS: All
unspecified
high
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Martin Kočí
URL:
Whiteboard:
Depends On:
Blocks: 1269194 1279571
TreeView+ depends on / blocked
 
Reported: 2015-10-15 21:21 UTC by Josh Carter
Modified: 2019-10-10 10:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1279571 (view as bug list)
Environment:
Last Closed: 2017-08-15 18:21:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Josh Carter 2015-10-15 21:21:52 UTC 
Description of problem:

I did two tests all with c3.large instance types, though that doesn't matter.

#1 Create an instance from ami-0ff3f13f and I was able to resize the root partition.  I then created an AMI from this instance and launched a new instance with this new AMI and was able to resize the root partition.  Just wanted to see if remaking a new AMI caused the issue, it didn't.

#2 I create an instance from ami-0ff3f13f and patched it (yum -y update), which is what we do as part of our hardening process. I then created an AMI from this instance and launched a new instance with this new AMI was NOT able to resize the root partition.

Because we must fully patch ami-0ff3f13f (and make other configuration changes) before turning it over to our internal customers, it's effectively broken.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.