Re: [atomic-devel] Help with testing AMI's

[Dusty Mabe <dustymabe gmail com>]

On Sun, Sep 07, 2014 at 12:40:24AM +0100, Karanbir Singh wrote:
> On 09/07/2014 12:28 AM, Dusty Mabe wrote:
> > On Wed, Aug 27, 2014 at 08:25:41AM +0100, Karanbir Singh wrote:
> > 
> >>
> >> Major issues outstanding:
> >>
> >> * need to redo the image build process to not use partitions, but to
> >> consume the entire block device
> > 
> > Can you elaborate on what the goal of this item is? 
> > 
> > Currently I notice an error because the partx in CentOS 7 (part of
> > util-linux-2.23.2-16.el7.x86_64) is older and has a bug that has been
> > fixed upstream[1]. This means that growpart will fail to run on /dev/vda3
> > (or /dev/xvda3 if you are running in EC2):
> > 
> > 2014-09-06 20:06:27,215 - util.py[WARNING]: Failed: growpart /dev/vda 3
> > 
> > Will the changes you are planning to make in some way affect this? 
> 
> No, but it should make it work in wider, different environments.
> 

Are you aware of the issue I referred to earlier? Basically this means that 
if there is more than one partition on the disk image (as is the case for these 
atomic images) then it won't get resized appropriately. As a result I end up only
using ~8G of disk space when I really allocated 20G, 30G, etc.. for the primary disk. 

I assume that this would also be an issue for RHEL7. Colin (or any other atomic
devs), have you experienced this before? Should I document this somewhere? 

Thanks,

Dusty