Bug 1016787

Summary: Image is not able to resize root fs without reboot
Product: Red Hat Enterprise Linux 6 Reporter: Jaroslav Henner <jhenner>
Component: guest-imagesAssignee: Joey Boggs <jboggs>
Status: CLOSED DUPLICATE QA Contact: Jaroslav Henner <jhenner>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.5CC: dgregor, jboggs, jgreguske, jhenner, leiwang, wshi, yeylon
Target Milestone: rc   
Target Release: 6.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-24 14:21:28 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: 1052453, 1100959    

Description Jaroslav Henner 2013-10-08 16:57:58 UTC
Description of problem:
The image is not able to get resized using cloud init, without a reboot

Version-Release number of selected component (if applicable):
rhel-server-x86_64-kvm-6.4_20130130.0-9-sda

How reproducible:
100%

Steps to Reproduce:
1. Boot the image with cloud-config specified below
2.
3.

Actual results:
root fs not resized

Expected results:
root fs resized

Additional info:
used this user-data for cloud-init:
#cloud-config
growpart:
  mode: auto
  devices: ['/']

Comment 3 RHEL Program Management 2013-10-14 01:43:49 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 Jaroslav Henner 2014-02-13 15:33:24 UTC
No it didn't. I don't think one should be required to modify an image for such a basic thing.

Comment 11 Jaroslav Henner 2014-05-24 14:21:28 UTC
Closing as a dup of 977028 because 977028 is going to be fixed in 6.5 and I think no new 6.4 guest image won't be released.

*** This bug has been marked as a duplicate of bug 977028 ***