Bug 1272253

Summary: EC2 Root partition does not get resized to the available space after updates are applied
Product: Red Hat Enterprise Linux 6 Reporter: Josh Carter <jocarter>
Component: ec2-imagesAssignee: Joey Boggs <jboggs>
Status: CLOSED WONTFIX QA Contact: Martin Kočí <mkoci>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.7CC: cww, harald, jgreguske
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1279571 (view as bug list) Environment:
Last Closed: 2017-08-15 18:21:09 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:
Bug Depends On:    
Bug Blocks: 1269194, 1279571    

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: