"vagrant halt" and "vagrant suspend" emit scary error messages about vagrant-vsphere

[agrauch]

The provider doesn't currently implement the halt and suspend commands. Kind of an ugly error but not too scary. Only up, destroy, and ssh have been implemented.

Updated the README to reflect this.

[dhirajdp]

is this issue fixed.?

Looks like it's fixed for halt but not for suspend.

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example
  > vagrant up
Bringing machine 'default' up with 'vsphere' provider...
==> default: Calling vSphere CloneVM with the following settings:
==> default:  -- Template VM: NSIDC/vm/Linux/SCM/trusty64-nsidc
==> default:  -- Target VM: NSIDC/vm/Linux/SCM/dev/mbrandt-vsphere-pr-testing
==> default: New virtual machine successfully cloned
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 172.18.225.242:22
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Rsyncing folder: /Users/mbrandt/projects/vagrant-vsphere-example/ => /vagrant

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example
  > vagrant halt
==> default: Attempting graceful shutdown of VM...

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example
  > vagrant up
Bringing machine 'default' up with 'vsphere' provider...
==> default: The VM is already created
==> default: Calling vSphere PowerOn
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 172.18.225.242:22
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Rsyncing folder: /Users/mbrandt/projects/vagrant-vsphere-example/ => /vagrant
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example
  > vagrant suspend
Vagrant attempted to call the action 'suspend' on the provider
'vSphere (42059517-6fb8-51ac-62da-bfb633468e8b)', but this provider doesn't support this action. This
is probably a bug in either the provider or the plugin calling this
action, and should be reported.

[dhirajdp]

thanks for reply

On Thu, Jun 2, 2016 at 7:51 PM, Michael Brandt [email protected]
wrote:

Looks like it's fixed for halt but not for suspend.

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example

vagrant up
Bringing machine 'default' up with 'vsphere' provider...
==> default: Calling vSphere CloneVM with the following settings:
==> default: -- Template VM: NSIDC/vm/Linux/SCM/trusty64-nsidc
==> default: -- Target VM: NSIDC/vm/Linux/SCM/dev/mbrandt-vsphere-pr-testing
==> default: New virtual machine successfully cloned
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 172.18.225.242:22
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Rsyncing folder: /Users/mbrandt/projects/vagrant-vsphere-example/ => /vagrant

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example

vagrant halt
==> default: Attempting graceful shutdown of VM...

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example

vagrant up
Bringing machine 'default' up with 'vsphere' provider...
==> default: The VM is already created
==> default: Calling vSphere PowerOn
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 172.18.225.242:22
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Rsyncing folder: /Users/mbrandt/projects/vagrant-vsphere-example/ => /vagrant
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.

mbrandt@nsidc-brandt ~/projects/vagrant-vsphere-example

vagrant suspend
Vagrant attempted to call the action 'suspend' on the provider
'vSphere (42059517-6fb8-51ac-62da-bfb633468e8b)', but this provider doesn't support this action. This
is probably a bug in either the provider or the plugin calling this
action, and should be reported.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#8 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ASyksxzoMBHulnxvnqSb7VLT7wcSmT7Bks5qHubMgaJpZM4A61OZ
.

Regards

DHIRAJ PANDEY