My procedure to use cucumber-chef v2.1.0.rc.6 with Vagrant

config.rb

################################################################################
# Cucumber-Chef
################################################################################

provider                        :vagrant
librarian_chef                  false
lxc_user                        "root"
lab_user                        "ubuntu"
prerelease                      true

artifacts                       ({ "chef-client-log" => "/var/log/chef/client.log",
                                   "chef-client-stacktrace" => "/var/chef/cache/chef-stacktrace.out" })


################################################################################
# Provider: AWS
################################################################################

aws[:aws_access_key_id]         = ""
aws[:aws_secret_access_key]     = ""

aws[:aws_ssh_key_id]            = ""
aws[:identity_file]             = "/"

aws[:region]                    = "-1"
aws[:availability_zone]         = "-1a"

#aws[:aws_instance_arch]         = "i386"
#aws[:aws_instance_disk_store]   = "instance-store"
#aws[:aws_instance_type]         = "m1.small"

#aws[:aws_security_group]        = "cucumber-chef"


################################################################################
# Provider: Vagrant
################################################################################

# TODO
vagrant[:identity_file]         = "~/.vagrant.d/insecure_private_key"

devopserver.feature

@devopserver
Feature: Perform test driven infrastructure with Cucumber-Chef
  In order to learn how to develop test driven infrastructure
  As an infrastructure developer
  I want to better understand how to use Cucumber-Chef

  Background:
    * I have a server called "devopserver"
    * "devopserver" is running "ubuntu" "precise"
    * "devopserver" has been provisioned
    * the following cookbooks have been uploaded:
      | cookbook | cookbook_path |
      | chef-client | ./cookbooks |
    * the "chef-client::default" recipe has been added to the "devopserver" run list
    * the chef-client has been run on "devopserver"
    * I ssh to "devopserver" with the following credentials:
      | username | keyfile |
      | root | ./.cucumber-chef/vagrant/id_rsa-vagrant |

  Scenario: Can connect to the provisioned server via SSH authentication
    When I run "hostname"
    Then I should see "devopserver" in the output

  Scenario: Default root shell is bash
    When I run "echo $SHELL"
    Then I should see "bash" in the output

  Scenario: Default gateway and resolver are using Cucumber-Chef Test Lab
    When I run "route -n | grep 'UG'"
      Then I should see "192.168.255.254" in the output
    When I run "cat /etc/resolv.conf"
      Then I should see "192.168.255.254" in the output
      And I should see "8.8.8.8" in the output
      And I should see "8.8.4.4" in the output

  Scenario: Primary interface is configured with my IP address and MAC address
    When I run "ifconfig eth0"
      Then I should see the "IP" of "devopserver" in the output
      And I should see the "MAC" of "devopserver" in the output

  Scenario: Local interface is not configured with my IP address or MAC address
    When I run "ifconfig lo"
      Then I should see "127.0.0.1" in the output
      And I should not see the "IP" of "devopserver" in the output
      And I should not see the "MAC" of "devopserver" in the output

  Scenario: Chef-Client is running as a daemon
    When I run "ps aux | grep [c]hef-client"
      Then I should see "chef-client" in the output
      And I should see "-d" in the output
      And I should see "-i 1800" in the output
      And I should see "-s 20" in the output

Gemfile

source "https://rubygems.org"

gem "cucumber-chef", :git => "git://github.com/Atalanta/cucumber-chef", :tag => "v2.1.0.rc.6"

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant::Config.run do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise64"
  config.vm.box_url = "http://files.vagrantup.com/precise64.box"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  # config.vm.box_url = "http://domain.com/path/to/above.box"

  # Boot with a GUI so you can see the screen. (Default is headless)
  # config.vm.boot_mode = :gui

  # Assign this VM to a host-only network IP, allowing you to access it
  # via the IP. Host-only networks can talk to the host machine as well as
  # any other machines on the same network, but cannot be accessed (through this
  # network interface) by any external networks.
  # config.vm.network :hostonly, "192.168.33.10"

  # Assign this VM to a bridged network, allowing you to connect directly to a
  # network using the host's network device. This makes the VM appear as another
  # physical device on your network.
  # config.vm.network :bridged

  # Forward a port from the guest to the host, which allows for outside
  # computers to access the VM, whereas host only networking does not.
  # config.vm.forward_port 80, 8080

  config.vm.forward_port 4000, 4000
  config.vm.forward_port 4040, 4040
  config.vm.forward_port 8787, 8787

  # Share an additional folder to the guest VM. The first argument is
  # an identifier, the second is the path on the guest to mount the
  # folder, and the third is the path on the host to the actual folder.
  # config.vm.share_folder "v-data", "/vagrant_data", "../data"

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file base.pp in the manifests_path directory.
  #
  # An example Puppet manifest to provision the message of the day:
  #
  # # group { "puppet":
  # #   ensure => "present",
  # # }
  # #
  # # File { owner => 0, group => 0, mode => 0644 }
  # #
  # # file { '/etc/motd':
  # #   content => "Welcome to your Vagrant-built virtual machine!
  # #               Managed by Puppet.\n"
  # # }
  #
  # config.vm.provision :puppet do |puppet|
  #   puppet.manifests_path = "manifests"
  #   puppet.manifest_file  = "base.pp"
  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles
  # path, and data_bags path (all relative to this Vagrantfile), and adding 
  # some recipes and/or roles.
  #
  # config.vm.provision :chef_solo do |chef|
  #   chef.cookbooks_path = "../my-recipes/cookbooks"
  #   chef.roles_path = "../my-recipes/roles"
  #   chef.data_bags_path = "../my-recipes/data_bags"
  #   chef.add_recipe "mysql"
  #   chef.add_role "web"
  #
  #   # You may also specify custom JSON attributes:
  #   chef.json = { :mysql_password => "foo" }
  # end

  # Enable provisioning with chef server, specifying the chef server URL,
  # and the path to the validation key (relative to this Vagrantfile).
  #
  # The Opscode Platform uses HTTPS. Substitute your organization for
  # ORGNAME in the URL and validation key.
  #
  # If you have your own Chef Server, use the appropriate URL, which may be
  # HTTP instead of HTTPS depending on your configuration. Also change the
  # validation key to validation.pem.
  #
  # config.vm.provision :chef_client do |chef|
  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  #   chef.validation_key_path = "ORGNAME-validator.pem"
  # end
  #
  # If you're using the Opscode platform, your validator client is
  # ORGNAME-validator, replacing ORGNAME with your organization name.
  #
  # IF you have your own Chef Server, the default validation client name is
  # chef-validator, unless you changed the configuration.
  #
  #   chef.validation_client_name = "ORGNAME-validator"
end

$ mkdir <project-home>
$ cd <project-home>
$ vi Gemfile

source "https://rubygems.org"
gem "cucumber-chef", :git => "git://github.com/Atalanta/cucumber-chef", :tag => "v2.1.0.rc.6"

$ bundle --path=vendor/bundle

$ mkdir .chef
$ bundle exec cucumber-chef init
$ vi .cucumber-chef/config.rb

provider :vagrant
prerelease true
vagrant[:identity_file] = "~/.vagrant.d/insecure_private_key"

$ mkdir -p .cucumber-chef/vagrant
$ touch .cucumber-chef/vagrant/knife.rb
$ bundle exec cucumber-chef displayconfig

$ bundle exec vagrant init
$ vi Vagrantfile

config.vm.box = "precise64"
config.vm.box_url = "http://files.vagrantup.com/precise64.box"

config.vm.forward_port 4000, 4000
config.vm.forward_port 4040, 4040
config.vm.forward_port 8787, 8787

$ bundle exec cucumber-chef setup

$ bundle exec cc-knife cookbook create chef-client
$ bundle exec cc-knife cookbook upload chef-client
$ bundle exec cucumber-chef create devopserver
$ vi features/devopserver/devopserver.feature

the "chef-client::default" recipe
keyfile:
./.cucumber-chef/vagrant/id_rsa-vagrant

$ bundle exec cucumber