Fix our vagrant-libvirt -based build setup vs. boot order configuration of non-Vagrant libvirt guests

$ http_proxy=http://10.36.24.33:3142 TAILS_BUILD_OPTIONS="ram extproxy gzipcomp" rake --trace vm:up ** Invoke vm:up (first_time) ** Invoke parse_build_options (first_time) ** Execute parse_build_options ** Invoke validate_http_proxy (first_time) ** Execute validate_http_proxy Using HTTP proxy: http://10.36.24.33:3142 ** Execute vm:up

This is the first time that the Tails builder virtual machine is
started. The virtual machine template is about 300 MB to download,
so the process might take some time.

Please remember to shut the virtual machine down once your work on
Tails is done:

    $ rake vm:halt

Bringing machine 'default' up with 'libvirt' provider...
default boot order: ["hd", "cdrom", "network"]
current: cdrom
default boot order: ["hd", "cdrom", "network"]
current: cdrom
default boot order: ["hd", "cdrom", "network"]
current: fd
/usr/lib/ruby/vendor_ruby/fog/libvirt/models/compute/server.rb:430:in `block in verify_boot_order': invalid boot order, possible values are: hd, network and/or cdrom (RuntimeError)
    from /usr/lib/ruby/vendor_ruby/fog/libvirt/models/compute/server.rb:427:in `each'
    from /usr/lib/ruby/vendor_ruby/fog/libvirt/models/compute/server.rb:427:in `verify_boot_order'
    from /usr/lib/ruby/vendor_ruby/fog/libvirt/models/compute/server.rb:48:in `initialize'
    from /usr/lib/ruby/vendor_ruby/fog/core/collection.rb:89:in `new'
    from /usr/lib/ruby/vendor_ruby/fog/core/collection.rb:89:in `new'
    from /usr/lib/ruby/vendor_ruby/fog/core/collection.rb:77:in `block in load'
    from /usr/lib/ruby/vendor_ruby/fog/core/collection.rb:77:in `each'
    from /usr/lib/ruby/vendor_ruby/fog/core/collection.rb:77:in `load'
    from /usr/lib/ruby/vendor_ruby/fog/libvirt/models/compute/servers.rb:11:in `all'
    from /usr/lib/ruby/vendor_ruby/vagrant-libvirt/action/set_name_of_domain.rb:18:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:95:in `block in finalize_action'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in run'
    from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/builtin/call.rb:53:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in run'
    from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:224:in `action_raw'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:199:in `block in action'
    from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:527:in `lock'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:185:in `call'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:185:in `action'
    from /usr/lib/ruby/vendor_ruby/vagrant/batch_action.rb:82:in `block (2 levels) in run'
'vagrant ["up"]' command failed: 1
zsh: exit 1     http_proxy=http://10.36.24.33:3142 TAILS_BUILD_OPTIONS="ram extproxy gzipcomp

The “current” and “default boot order” warnings above were added by me, in /usr/lib/ruby/vendor_ruby/fog/libvirt/models/compute/server.rb, in order to debug this.

Attachments

• tails-stable.xml
• fog-libvirt-boot-order.patch

Parent Task: #7526 (closed)

Original created by @intrigeri on 11155 (Redmine)