kitchen does not create needed interface. no errors

[ror6ax]

My kitchen.yml features this:

    - name: default
      network:
         - ["forwarded_port", {guest: 80, host: 8080}]
         - ["private_network", {ip: "192.168.1.10"}]

It results in your usual forwarding, no private network. What is worse, no errors, all green,
However if I get the whole network part into first driver declaraion, like this:

---
driver:
    name: vagrant
    network:
        - ["private_network",{ip: '192.168.1.10'}]

...it works fine, my interface is in place.

[scarolan]

I've confirmed the same problem on OSX, using ChefDK 4.0. Also tried rolling back to ChefDK 3.6, which didn't make any difference. I also confirmed what ror6ax said, moving the ip address up into the main driver: section works, but is a bummer because you can't have different ips in multiple suites.

[cybermerc]

I'm also seeing this issue on OSX. I use multiple suites with various IP and need them to be able to talk to each other for proper testing. Currently I can not find any way around this bug. In my case using this kitchen.yml file it uses the first IP noted in the first test suite on all suites.

Using this example all test suites use the IP 192.168.0.21
https://github.com/rackspace-cookbooks/pg-multi/blob/master/.kitchen.yml

Let me know if anyone is able to find a work around or know of something I'm doing wrong. This kitchen.yml was working as late as Dec 2014 so not sure when bug was introduced.

[nimeshsubramanian]

Im my experience this normally happens when the spacing is off in your kitchen.yml file.

[cheeseplus]

Is this still an issue? Also think this may end up being more of a kitchen-vagrant issue rather than a core TK issue.

[cheeseplus]

Definitely not a core kitchen issue and almost definitely issues with the configs themselves. If still experiencing please open a new one on kitchen-vagrant with current versions.