Vagrant_ip on 'dhcp' results in error/no ip.

[Xilonz]

• I've read the guidelines for Contributing to Roots Projects
• This is a feature request
• This is a bug report
• This request isn't a duplicate of an existing issue
• I've read the docs and followed them (if applicable)
• This is not a personal support request that should be posted on the Roots Discourse forums

---

What is the current behavior?

hostname -I | cut -d ' ' -f 2 returns nothing.

What is the expected or desired behavior?

A better logging output and/or it actually working.

hostname -I | cut -d ' ' -f 1 returns its actual ip.

Why not use vm.provider.driver.read_guest_ip()['ip'] instead? I don't have VirtualBox (or any other than hyper-v), but the VirtualBox driver does have the same function.

---

Bug report

==> default: [vagrant-hostmanager:guests] Updating hosts file on active guest virtual machines...
c:/Users/steen/git/trellis-hyper-v-test/trellis/Vagrantfile:40:in `block (3 levels) in <top (required)>': undefined method `[]' for nil:NilClass (NoMethodError)

Please describe your local environment:

Ansible version: 2.5.1
OS: Windows 10, build 17763
Vagrant version: 2.2.3
VM: Hyper-V

Where did the bug happen? Development or remote servers?

Development

Is there a related Discourse thread or were any utilized (please link them)?

I've documented my experiences with hyper-v here

[swalkinshaw]

I didn't even know about vm.provider.driver.read_guest_ip. That does seem better...

Although Trellis does technically support parallels and vmware. I searched Vagrant and read_guest_ip only appears in VB and HyperV. Not sure how much this matters though?

[swalkinshaw]

@Xilonz are you still using Trellis + HyperV? Would be able to test a few variations on this if I provide them?