{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/7948","repository_url":"https://api.github.com/repos/mitchellh/vagrant","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/7948/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/7948/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/7948/events","html_url":"https://github.com/mitchellh/vagrant/issues/7948","id":186160125,"number":7948,"title":"Port collision detection broken under VMware Fusion 8.5.1","user":{"login":"sirn","id":4061,"avatar_url":"https://avatars.githubusercontent.com/u/4061?v=3","gravatar_id":"","url":"https://api.github.com/users/sirn","html_url":"https://github.com/sirn","followers_url":"https://api.github.com/users/sirn/followers","following_url":"https://api.github.com/users/sirn/following{/other_user}","gists_url":"https://api.github.com/users/sirn/gists{/gist_id}","starred_url":"https://api.github.com/users/sirn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sirn/subscriptions","organizations_url":"https://api.github.com/users/sirn/orgs","repos_url":"https://api.github.com/users/sirn/repos","events_url":"https://api.github.com/users/sirn/events{/privacy}","received_events_url":"https://api.github.com/users/sirn/received_events","type":"User","site_admin":false},"labels":[{"id":25816,"url":"https://api.github.com/repos/mitchellh/vagrant/labels/bug","name":"bug","color":"e11d21","default":true},{"id":78408650,"url":"https://api.github.com/repos/mitchellh/vagrant/labels/provider/vmware","name":"provider/vmware","color":"bfe5bf","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":28,"created_at":"2016-10-30T20:16:38Z","updated_at":"2016-11-22T22:12:32Z","closed_at":null,"body":"### Vagrant version\r\n\r\n```\r\n$ vagrant -v\r\nVagrant 1.8.6\r\n\r\n$ vagrant plugin list\r\nvagrant-scp (0.5.7)\r\nvagrant-share (1.1.5, system)\r\nvagrant-vmware-fusion (4.0.14)\r\n```\r\n### Host operating system\r\n\r\nmacOS Sierra 10.12.1\r\n### Guest operating system\r\n\r\nUbuntu 12.04 (VMware Fusion 8.5.1)\r\n### Vagrantfile\r\n\r\n``` ruby\r\nVagrant.configure(\"2\") do |config|\r\n  config.vm.box = \"hashicorp/precise64\"\r\n  config.vm.network \"forwarded_port\", guest: 80, host: 8080\r\nend\r\n```\r\n### Debug output\r\n\r\nhttps://gist.github.com/sirn/b885d89d02ec1b426b91beb35a65d34f\r\n### Expected behavior\r\n\r\nNo port collision.\r\n### Actual behavior\r\n\r\nVagrant detected port collision.\r\n### Steps to reproduce\r\n1. Run `vagrant up` with the provided Vagrantfile, no port collision should happen in this step.\r\n2. Run `vagrant halt` to shutdown the machine.\r\n3. Run `vagrant up` again.\r\n\r\n---\r\n\r\nIn `/Library/Preferences/VMware Fusion/vmnet8/nat.conf`, this is the `[incomingtcp]` section after the first `vagrant up` run (port 8080 successfully forwarded):\r\n\r\n``` ini\r\n[incomingtcp]\r\n\r\n# Use these with care - anyone can enter into your VM through these...\r\n# The format and example are as follows:\r\n#<external port number> = <VM's IP address>:<VM's port number>\r\n#8080 = 172.16.3.128:80\r\n# VAGRANT-BEGIN: /Users/sirn/Desktop/foobar/.vagrant/machines/default/vmware_fusion/cb8daaaa-02d8-4707-9708-e8c5e30d17dd/precise64.vmx\r\n8080 = 192.168.229.128:80\r\n2222 = 192.168.229.128:22\r\n# VAGRANT-END: /Users/sirn/Desktop/foobar/.vagrant/machines/default/vmware_fusion/cb8daaaa-02d8-4707-9708-e8c5e30d17dd/precise64.vmx\r\n```\r\n\r\nThen the `[incomingtcp]` section after the second `vagrant up` that resulted in an error:\r\n\r\n``` ini\r\n[incomingtcp]\r\n\r\n# Use these with care - anyone can enter into your VM through these...\r\n# The format and example are as follows:\r\n#<external port number> = <VM's IP address>:<VM's port number>\r\n#8080 = 172.16.3.128:80\r\n2222 = 192.168.229.128:22\r\n8080 = 192.168.229.128:80\r\n```\r\n\r\nI've tried nuking `/Library/Preferences/VMware Fusion/networking*` and `/Library/Preferences/VMware Fusion/vmnet*` and re-run VMware Fusion to have it populate the configuration prior to running, but still the same result.\r\n\r\nI can also reproduce this issue in my other machine running exactly the same setup as well.\r\n"},"comment":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/262381420","html_url":"https://github.com/mitchellh/vagrant/issues/7948#issuecomment-262381420","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/7948","id":262381420,"user":{"login":"vdanen","id":643587,"avatar_url":"https://avatars.githubusercontent.com/u/643587?v=3","gravatar_id":"","url":"https://api.github.com/users/vdanen","html_url":"https://github.com/vdanen","followers_url":"https://api.github.com/users/vdanen/followers","following_url":"https://api.github.com/users/vdanen/following{/other_user}","gists_url":"https://api.github.com/users/vdanen/gists{/gist_id}","starred_url":"https://api.github.com/users/vdanen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vdanen/subscriptions","organizations_url":"https://api.github.com/users/vdanen/orgs","repos_url":"https://api.github.com/users/vdanen/repos","events_url":"https://api.github.com/users/vdanen/events{/privacy}","received_events_url":"https://api.github.com/users/vdanen/received_events","type":"User","site_admin":false},"created_at":"2016-11-22T22:12:32Z","updated_at":"2016-11-22T22:12:32Z","body":"Once I cleaned up the networking file and vmnet8/nat.conf I could get 'vagrant up' to proceed further but there's still something funky going on in that now it reports this:\r\n\r\n```\r\nvdanen@sif:~/git/otter|master⚡ ⇒  vagrant reload\r\n==> otter: Attempting graceful shutdown of VM...\r\n==> otter: Checking if box 'puppetlabs/centos-7.0-64-nocm' is up to date...\r\n==> otter: There was a problem while downloading the metadata for your box\r\n==> otter: to check for updates. This is not an error, since it is usually due\r\n==> otter: to temporary network problems. This is just a warning. The problem\r\n==> otter: encountered was:\r\n==> otter:\r\n==> otter:\r\n==> otter:\r\n==> otter: If you want to check for box updates, verify your network connection\r\n==> otter: is valid and try again.\r\n==> otter: Skipping vmnet device verification, verify_vmnet is set to false.\r\n==> otter: Preparing network adapters...\r\n==> otter: Starting the VMware VM...\r\n==> otter: Waiting for machine to boot. This may take a few minutes...\r\n    otter: SSH address: 172.16.154.159:22\r\n    otter: SSH username: vagrant\r\n    otter: SSH auth method: private key\r\n    otter: Warning: Connection refused. Retrying...\r\n==> otter: Machine booted and ready!\r\n==> otter: Forwarding ports...\r\n    otter: -- 80 => 5000\r\n    otter: -- 3306 => 3306\r\n    otter: -- 22 => 2222\r\n==> otter: Configuring network adapters within the VM...\r\nThe following SSH command responded with a non-zero exit status.\r\nVagrant assumes that this means the command failed!\r\n\r\n# Restart network\r\nservice network restart\r\n\r\n\r\nStdout from the command:\r\n\r\nRestarting network (via systemctl):  [FAILED]\r\n\r\n\r\nStderr from the command:\r\n\r\nJob for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.\r\n```\r\n\r\nI have no idea what this means or why the network is not coming up.  Going to try rebooting again to see if that helps."}}
{"actor":{"display_login":"vdanen"}}