The centos/7 image for vagrant-libvirt need to bigger than 41GB

Bug #1511265 reported by Eohyung Lee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Low
Martin André

Bug Description

deploy@host:~/kolla/dev/vagrant$ vagrant up
Generating public/private rsa key pair.
Your identification has been saved in ./vagrantkey.
Your public key has been saved in ./vagrantkey.pub.
The key fingerprint is:
2c:42:62:78:94:11:f4:d7:bb:eb:b2:ab:e7:73:ab:7b this-is-vagrant
The key's randomart image is:
+--[ RSA 2048]----+
| .=+ |
| o.. . |
|. + o . . |
| o o . . . |
| . . S |
| . . . |
| . |
| + E. |
| .+*@+. |
+-----------------+
Bringing machine 'operator' up with 'libvirt' provider...
==> operator: Box 'centos/7' could not be found. Attempting to find and install...
    operator: Box Provider: libvirt
    operator: Box Version: >= 0
==> operator: Loading metadata for box 'centos/7'
    operator: URL: https://atlas.hashicorp.com/centos/7
==> operator: Adding box 'centos/7' (v1509.01) for provider: libvirt
    operator: Downloading: https://atlas.hashicorp.com/centos/boxes/7/versions/1509.01/providers/libvirt.box
==> operator: Successfully added box 'centos/7' (v1509.01) for 'libvirt'!
/opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/config.rb:92:in `block in missing_interpolation_argument_handler': missing interpolation argument :box_virtual_size in "Ignoring requested virtual disk size of '%{requested}' as it is below\nthe minimum box image size of '%{box_virtual_size}'." ({:requested=>40, :minimum=>41} given) (I18n::MissingInterpolationArgument)
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:29:in `call'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:29:in `block in interpolate_hash'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:21:in `gsub'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:21:in `interpolate_hash'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:17:in `interpolate'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:152:in `interpolate'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:41:in `translate'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n.rb:158:in `block in translate'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n.rb:154:in `catch'
 from /opt/vagrant/embedded/gems/gems/i18n-0.7.0/lib/i18n.rb:154:in `translate'
 from /home/deploy/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/handle_box_image.rb:45:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /home/deploy/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/handle_storage_pool.rb:50:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /home/deploy/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
 from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

I checked latest centos/7 for vagrant-libvirt image and I found it has virtual_size: 41.

deploy@host:~/.vagrant.d/boxes/centos-VAGRANTSLASH-7/1509.01/libvirt$ cat metadata.json
{"provider": "libvirt", "format": "qcow2", "virtual_size": 41}

Changed in kolla:
status: New → Triaged
importance: Undecided → Low
milestone: none → mitaka-1
Martin André (mandre)
Changed in kolla:
status: Triaged → Confirmed
assignee: nobody → Martin André (mandre)
Revision history for this message
Martin André (mandre) wrote :

To give a bit of context, the centos/7 image was recently updated with a default disk size of 40GB. It used to only come with 10GB so we had to increase the disk size during provisioning to support building kolla images from the operator node.

Now that the image has acceptable default disk size, we should stick with it and remove the disk resize from provision script.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/240704

Changed in kolla:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla (master)

Change abandoned by Eohyung Lee (<email address hidden>) on branch: master
Review: https://review.openstack.org/240168
Reason: @Martin
Sure, no ploblem.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/240704
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=95517f01fc7d082e3a48a8e282854ea4d537760a
Submitter: Jenkins
Branch: master

commit 95517f01fc7d082e3a48a8e282854ea4d537760a
Author: Martin André <email address hidden>
Date: Sun Nov 1 21:29:36 2015 +0900

    Use default disk image size for centos/7

    Latest centos/7 image from atlas now comes with 40 GB disk size which
    is equal to the virtual_size we specify in the Vagrantfile. Libvirt
    provider doesn't like it and produces an ugly stacktrace.

    The new default value now sufficient run kolla properly and we can
    remove the code that artificially increased the disk size.

    Change-Id: I7a645543cfcc027b4a3e0d02d8e7f436d8410ec5
    Backport: Liberty
    Closes-Bug: #1511265

Changed in kolla:
status: In Progress → Fix Committed
Sam Yaple (s8m)
Changed in kolla:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (stable/liberty)

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/269481

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/liberty)

Reviewed: https://review.openstack.org/269481
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=cf4ecb11b0b736a972c7bcb71de108fcba042d0f
Submitter: Jenkins
Branch: stable/liberty

commit cf4ecb11b0b736a972c7bcb71de108fcba042d0f
Author: Martin André <email address hidden>
Date: Sun Nov 1 21:29:36 2015 +0900

    Use default disk image size for centos/7

    Latest centos/7 image from atlas now comes with 40 GB disk size which
    is equal to the virtual_size we specify in the Vagrantfile. Libvirt
    provider doesn't like it and produces an ugly stacktrace.

    The new default value now sufficient run kolla properly and we can
    remove the code that artificially increased the disk size.

    Change-Id: I7a645543cfcc027b4a3e0d02d8e7f436d8410ec5
    Backport: Liberty
    Closes-Bug: #1511265
    (cherry picked from commit 95517f01fc7d082e3a48a8e282854ea4d537760a)

tags: added: in-stable-liberty
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.