Comment 8 for bug 1407417

We encounter the problem using the below kitchen.yml configuration (although it seems that you would want to dive into more detailed neutron configuration examples?):

driver:
  name: openstack
  openstack_username: <%= ENV['OS_USERNAME'] %>
  openstack_tenant: <%= ENV['OS_TENANT_NAME'] %>
  openstack_api_key: <%= ENV['OS_PASSWORD'] %>
  openstack_auth_url: <%= "#{ENV['OS_AUTH_URL']}/tokens" %>
  availability_zone: Z1
  require_chef_omnibus: true
  network_ref: kitchen-net
  floating_ip_pool: ext-net
  image_ref: Ubuntu 14.04
  disable_ssl_validation: true
  flavor_ref: m1.kitchen
  username: ubuntu

platforms:
  - name: ubuntu-14.04

After `kitchen create`, from the users perspective it goes like this:

-----> Creating <default-ubuntu-1404>...
       OpenStack instance with ID of <195775bb-8c50-4bfd-83fb-f3e164daa152> is ready.
       Attaching floating IP from <ext-net> pool
       Attaching floating IP <1.2.3.4>
>>>>>> Create failed on instance <default-ubuntu-1404>.
>>>>>> Please see .kitchen/logs/default-ubuntu-1404.log for more details
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Expected([200, 202]) <=> Actual(400 Bad Request)
excon.error.response
  :body => "{\"badRequest\": {\"message\": \"No nw_info cache associated with instance\", \"code\": 400}}"
  :headers => {
    "Content-Length" => "85"
    "Content-Type" => "application/json; charset=UTF-8"
    "Date" => "Sat, 05 Dec 2015 12:28:34 GMT"
    "X-Compute-Request-Id" => "req-ca32ce40-9450-41d1-a26e-8db22eadb4f5"
  }
  :local_address => "1.2.3.5"
  :local_port => 41784
  :reason_phrase => "Bad Request"
  :remote_ip => "1.2.3.6"
  :status => 400
  :status_line => "HTTP/1.1 400 Bad Request\r\n"

>>>>>> ----------------------

Will provide more neutron plumbing details later.