Bug 1260800 - Fedora 22 Cloud vagrant image does not extend filesystem to disk size
Fedora 22 Cloud vagrant image does not extend filesystem to disk size
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: vagrant (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vít Ondruch
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-07 17:13 EDT by Victor Costan
Modified: 2015-09-08 02:08 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-09-08 02:08:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Victor Costan 2015-09-07 17:13:27 EDT
Description of problem:

The Vagrant image for Fedora 22 cloud does not extend the filesystem to fill up the entire disk.

Version-Release number of selected component (if applicable):
https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-virtualbox.box

How reproducible:
Always

Steps to Reproduce:
1. Set up a new Vagrant box using the Fedora 22 cloud base box.
2. vagrant ssh
3. Inspect the partition table.

Actual results:

[vagrant@localhost ~]$ sudo fdisk -l /dev/sda
Disk /dev/sda: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe02b2711

Device     Boot Start     End Sectors Size Id Type
/dev/sda1  *     2048 6146047 6144000   3G 83 Linux


Expected results:

I'd expect to see the filesystem grown to fill the virtual disk.

Additional info:

This is a serious obstacle to deploying Fedora Cloud for me. I need to be able to test things out in a Vagrant box before pushing things out to production. The 3G filesystem makes it impossible for me to load everything I need into the VM.

Please let me know if there is any other information I can provide to help narrow this down.
Comment 1 Victor Costan 2015-09-07 17:36:42 EDT
I also filed this on the Cloud SIG Trac.
https://fedorahosted.org/cloud/ticket/120

This is based on the trail in the bug below, which also concerns the cloud base vagrant image.
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1225630
Redirect 1: https://fedorahosted.org/rel-eng/ticket/6192
Comment 2 Vít Ondruch 2015-09-08 02:08:16 EDT
(In reply to Victor Costan from comment #1)
> I also filed this on the Cloud SIG Trac.
> https://fedorahosted.org/cloud/ticket/120

Thanks. That is the right place. This tracker is just for Vagrant package issues.

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