{"action":"created","issue":{"url":"https://api.github.com/repos/CentOS/sig-cloud-instance-build/issues/134","repository_url":"https://api.github.com/repos/CentOS/sig-cloud-instance-build","labels_url":"https://api.github.com/repos/CentOS/sig-cloud-instance-build/issues/134/labels{/name}","comments_url":"https://api.github.com/repos/CentOS/sig-cloud-instance-build/issues/134/comments","events_url":"https://api.github.com/repos/CentOS/sig-cloud-instance-build/issues/134/events","html_url":"https://github.com/CentOS/sig-cloud-instance-build/issues/134","id":352124598,"node_id":"MDU6SXNzdWUzNTIxMjQ1OTg=","number":134,"title":"vmware-esxi \"Failed, timeout waiting for \"running\".\"","user":{"login":"mplinuxgeek","id":283878,"node_id":"MDQ6VXNlcjI4Mzg3OA==","avatar_url":"https://avatars3.githubusercontent.com/u/283878?v=4","gravatar_id":"","url":"https://api.github.com/users/mplinuxgeek","html_url":"https://github.com/mplinuxgeek","followers_url":"https://api.github.com/users/mplinuxgeek/followers","following_url":"https://api.github.com/users/mplinuxgeek/following{/other_user}","gists_url":"https://api.github.com/users/mplinuxgeek/gists{/gist_id}","starred_url":"https://api.github.com/users/mplinuxgeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mplinuxgeek/subscriptions","organizations_url":"https://api.github.com/users/mplinuxgeek/orgs","repos_url":"https://api.github.com/users/mplinuxgeek/repos","events_url":"https://api.github.com/users/mplinuxgeek/events{/privacy}","received_events_url":"https://api.github.com/users/mplinuxgeek/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-08-20T13:01:06Z","updated_at":"2018-08-29T02:58:51Z","closed_at":null,"author_association":"NONE","body":"vagrant up fails when using vmware-esxi plugin.\r\n\r\nThe error is caused because the plugin is waiting for the VM state to change to running which it never does because there are no VMware tools in the image.\r\n\r\nI logged into the image via ESXi console and installed and started open-vm-tools, after this has been done vagrant successfully provisions the new VM.\r\n\r\nI can test this with VMware workstation when I get to work tomorrow, but I can't test Fusion or vCenter however I expect they will all behave the same.\r\n\r\n```\r\nvagrant@vmtest01:~/vmmgt01$ vagrant up --provider=vmware_esxi\r\n\r\nBringing machine 'vmmgt01' up with 'vmware_esxi' provider...\r\n==> vmmgt01: Virtual Machine will be built.\r\nVMware ovftool 4.3.0 (build-7948156)\r\n==> vmmgt01: ---   --- ESXi Summary ---\r\n==> vmmgt01: --- ESXi host       : X.X.X.X\r\n==> vmmgt01: --- Virtual Network : [\"LAN\"]\r\n==> vmmgt01: --- Disk Store      : datastore1\r\n==> vmmgt01: --- Resource Pool   : /\r\n==> vmmgt01: ---  --- Guest Summary ---\r\n==> vmmgt01: --- VM Name         : vmmgt01\r\n==> vmmgt01: --- Box             : centos/7\r\n==> vmmgt01: --- Box Ver         : 1804.02\r\n==> vmmgt01: --- Memsize (MB)    : 4096\r\n==> vmmgt01: --- CPUS            : 2\r\n==> vmmgt01: --- Guest OS type   : linux\r\n==> vmmgt01: ---   --- Guest Build ---\r\nOpening VMX source: /home/vagrant/.vagrant.d/boxes/centos-VAGRANTSLASH-7/1804.02/vmware_desktop/ZZZZ_vmmgt01.vmx\r\nOpening VI target: vi://user@X.X.X.X:443/\r\nDeploying to VI: vi://user@X.X.X.X:443/\r\nTransfer Completed                    \r\nCompleted successfully\r\n==> vmmgt01: --- VMID            : 48\r\n==> vmmgt01: --- VM has been Powered On...\r\n==> vmmgt01: --- Waiting for state \"running\"\r\nThere was an error.\r\n  Failed, timeout waiting for \"running\".\r\n```\r\n\r\n**Update:**\r\nI wrote a quick script to check if the server is running in VMware if yes then install and start open-vm-tools, perhaps this could be added to the image on first boot? or as a @reboot cron job that deletes itself after the first run?\r\n\r\n```\r\n#!/bin/bash\r\nif dmidecode -s system-product-name | grep --quiet -i vmware; then\r\n  yum install -y open-vm-tools\r\n  systemctl enable vmtoolsd.service\r\n  systemctl start vmtoolsd.service\r\nfi\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/CentOS/sig-cloud-instance-build/issues/comments/416807626","html_url":"https://github.com/CentOS/sig-cloud-instance-build/issues/134#issuecomment-416807626","issue_url":"https://api.github.com/repos/CentOS/sig-cloud-instance-build/issues/134","id":416807626,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNjgwNzYyNg==","user":{"login":"mvermaes","id":4127064,"node_id":"MDQ6VXNlcjQxMjcwNjQ=","avatar_url":"https://avatars1.githubusercontent.com/u/4127064?v=4","gravatar_id":"","url":"https://api.github.com/users/mvermaes","html_url":"https://github.com/mvermaes","followers_url":"https://api.github.com/users/mvermaes/followers","following_url":"https://api.github.com/users/mvermaes/following{/other_user}","gists_url":"https://api.github.com/users/mvermaes/gists{/gist_id}","starred_url":"https://api.github.com/users/mvermaes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mvermaes/subscriptions","organizations_url":"https://api.github.com/users/mvermaes/orgs","repos_url":"https://api.github.com/users/mvermaes/repos","events_url":"https://api.github.com/users/mvermaes/events{/privacy}","received_events_url":"https://api.github.com/users/mvermaes/received_events","type":"User","site_admin":false},"created_at":"2018-08-29T02:58:51Z","updated_at":"2018-08-29T02:58:51Z","author_association":"CONTRIBUTOR","body":"At least from [September 2016](https://lists.centos.org/pipermail/centos-devel/2016-September/015169.html), I think open-vm-tools has not been preinstalled in the box. Will be great to see it included.\r\n\r\nThe Tools aren't actually required to use 'stock' Vagrant (ie. just Workstation and Fusion with rsync), other than to get bidirectional synced folder support. But like you said, I think it should be safe to include them, and it seems like it would also resolve the vmware-esxi plugin issue that @mplinuxgeek reported.\r\n\r\nI still do what I can to [test the VMware images in Fusion](https://github.com/mvermaes/centos-vmware-tools) when there is a new box release btw :)"}}
{"actor":{"display_login":"mvermaes"}}