Bug 1158631

Summary:	Atomic images disk too small, growpart doesn't work with LVM
Product:	[Fedora] Fedora	Reporter:	Joe Brockmeier <jzb>
Component:	distribution	Assignee:	Václav Pavlín <vpavlin>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	21	CC:	agrimm, dennis, jzb, mattdm, walters
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-02 04:35:58 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:

Description Joe Brockmeier 2014-10-29 18:23:40 UTC

Description of problem:

Tested TC2 for the Atomic image (Fedora-Cloud-Atomic-20141028-21_Beta.x86_64.qcow2) and it comes with a 3GB disk using LVM. 

Since it's lvm, we can't use growpart to expand the disk - and 3GB is woefully insufficient. Doing "docker pull fedora" with no additional data on the system will fill the disk.

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

Fedora 21 Beta

How reproducible:

Just spin up an instance of Fedora 21 Atomic beta and try pulling any docker images of any size. 

Steps to Reproduce:
1. Start the Atomic image
2. run docker pull fedora 
3. wait for this to complete, it will eventually error out due to insufficient space.

Actual results:

Not enough space. 

Expected results:

You should be able to pull several docker images and work with several images on the default image without any need to make allowances for space.

Additional info:

We need to either fix growpart for final, or change the Atomic image so that it's not using LVM.

Comment 1 Fedora Blocker Bugs Application 2014-10-29 18:27:28 UTC

Proposed as a Freeze Exception for 21-beta by Fedora user jzb using the blocker tracking app because:

 As currently configured, the Atomic image is not usable out of the gate. It lacks space to even work with one Docker image, and LVM/growpart are not compatible, so it's non-trivial to expand the disk size.

Comment 2 Matthew Miller 2014-10-29 18:33:59 UTC

I think we missed the RC3 compose here. A quick fix is to expand the base size, since that's easy, and I'm in favor of that in theory since it only should affect Atomic (only possible exception would be if the size impacts the compose process, which I guess is non-zero; it will be a little slower). Output image is compressed, so more zeros don't have any impact on mirrors or anything.

Comment 3 Matthew Miller 2014-10-29 18:37:39 UTC

Colin, is there a compelling reason for this to be LVM? Going back to plain partitions seems like the easiest approach.

Comment 4 Matthew Miller 2014-10-29 18:51:58 UTC

Apparently there is supposed to be something called docker-storage-setup which will automatically configure the LVM space to be docker storage, and basically everything is working as planned here -- except there is no docker-storage-setup.

Comment 5 Matthew Miller 2014-10-29 19:00:49 UTC

I'm going to remove the freeze exception proposal for now until we get this straightened out. I guess it will have to go in post-beta for final. Since Atomic is non-blocking and (mostly) stands on its own, I guess prioritizing adding that is the best thing we can do now, and documenting what steps users will need to take to configure LVM properly by hand in the beta.

Comment 6 Fedora End Of Life 2015-11-04 10:14:56 UTC

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-12-02 04:36:02 UTC

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.