require_chef_omnibus is ignored

[test-kitchen]

require_chef_omnibus is ignored

[lxndrp]

I also left a comment on #4 on this, as cross reference.

[fnichol]

Sorry about the confusion here, did you happen to have a .kitchen.yml config I could see as an example?

In release 0.10.0 we refactored the driver so that Test Kitchen treats a Vagrant VM as just another SSH-connected host. In this way the Vagrant driver becomes more like the other drivers (using more implementation from the base SSH driver) and less of a special case.

The implication of this refactoring means that Test Kitchen installs the Omnibus package the same way it would for the EC2, Rackspace, Docker, and LXC drivers (etc.).

By chance are do you have use_vagrant_provision: true set in your .kitchen.yml?

[atomic-penguin]

@fnichol, I must be missing something, because when I do a test-kitchen run with master. Omnibus never gets installed.

Also have:
vagrant: 1.2.4
kitchen-vagrant: 0.11.1
vagrant-omnibus: 1.1.1

Tried setting require_chef_omnibus: true, use_vagrant_provision: true, both individually and together. Tried @thielena's patch, but for some reason, I'm just not getting omnibus in there for the test-kitchen run. Upgraded to vagrant 1.3.0, and ran into issue #40.

How does one get omnibus installed, post 0.10.0 refactor, because I'm actually kind of lost on what to try next?

EDIT: finally got it working with this patch, must have been something stale in ~/.vagrant.d or /.kitchen. shrugs

NINJA EDIT:
require_chef_omnibus: latest works with the patch, while require_chef_omnibus: true does not.

@fnichol, I'm using following versions:

vagrant (1.2.4)
vagrant-berkshelf (1.3.3)
vagrant-omnibus (1.1.0)
kitchen-vagrant (0.11.0)

.kitchen.yml as follows:

---
driver_plugin: vagrant
driver_config:
  use_vagrant_berkshelf_plugin: true
  use_vagrant_provision: true
  require_chef_omnibus: latest
  customize:
     memory: 2048

platforms:
- name: centos-6.4
  driver_config:
    box: opscode-centos-6.4
    box_url: https://opscode-vm-bento.s3.amazonaws.com/vagrant/opscode_centos-6.4_provisionerless.box
    network:
    - ["forwarded_port", {guest: 8080, host: 8080}]

- name: ubuntu-12.04
  driver_config:
    box: opscode-ubuntu-12.04
    box_url: https://opscode-vm-bento.s3.amazonaws.com/vagrant/opscode_ubuntu-12.04_provisionerless.box
    network:
    - ["forwarded_port", {guest: 8080, host: 8080}]

suites:
- name: default
  data_bags_path: "test/data_bags"
  run_list: ["recipe[testcookbook]"]
  attributes:

[nitinmohan87]

@fnichol If we have only require_chef_omnibus option set, the chef omnibus installation is take care of in the test-kitchen. But using use_vagrant_provision option bypasses test-kitchen convergence and uses vagrant provisioner - https://github.com/opscode/kitchen-vagrant/blob/master/lib/kitchen/driver/vagrant.rb#L59-L66

If we set use_vagrant_provision, the converge phase assumes that chef is installed in the VM which may not be true.

Pull request #35 fixes this issue. It adds the c.omnibus.chef_version to the Vagrantfile so that the converge phase actually installs chef when both use_vagrant_provision and require_chef_omnibus are set.

The same pull request also takes care of #44 to some extent. We would want to use additional vagrant plugins (take vagrant-ohai plugin for example) in our development.

[sethvargo]

Please see my comment on #35