search

Azure / vagrant-azure

Enable Vagrant to manage virtual machines in Microsoft Azure
MIT License
315 stars 112 forks source link

pre8 NSG and interface #198

Open njappboy opened 7 years ago

njappboy commented 7 years ago

Vagrant version: Vagrant 1.9.5 vagrant plugin list

vagrant-azure (2.0.0.pre8)
  - Version Constraint: 2.0.0.pre8
vagrant-digitalocean (0.9.1)
vagrant-docker-compose (1.3.0)
vagrant-share (1.1.8, system)
vagrant-vbguest (0.13.0)

vagrant box list

azure              (azure, 0)
# truncated for brevity

I've tried upgrade to the pre8 version multiple times only to hit the same issue every attempt. I've remove the azure dummy box and removed pre7.

I install the latest dummy box and then install pre8, following the README instructions.

The issue I'm seeing is related to the NSG not being associated with the network interface.

I can vagrant ssh into the VM and see the http services running. Local wget and curl requests work from an ssh session using the machine's host name.
The same requests fail when attempting to use the pip fqdn to reach the same port. I've confirmed that the inbound/outbound rules required to access the port are configured.

The same project works flawlessly with pre7 plugin version.

Any help would be appreciated as I would like to take advantage of the new optional vagrant-azure parameters to automating testing.

Please let me know if further information is required.

njappboy commented 7 years ago

Wondering if this PR fixes the issue I'm experiencing.

Made the changes outlined in the PR manually via azure portal and all is well once again. Steps

Update: confirmed that using the wildcard for the 'source' port via the portal was all that was required to return my vagrant azure project back to working order.

Any timeline for when this patch will be released?