4

When I run vagrant global-status, I see that some of my machines are in the state "preparing", which I have not seen from global-status before. What does this status mean? It seems to change to running after I check on the status of the server specifically.

$ vagrant global-status
id       name         provider state     directory
-----------------------------------------------------------------------------
1b9c91d  arthur       aws    running   /Users/afarrell/projects/saltmarsh
824fc08  sir-lancelot aws    preparing /Users/afarrell/projects/saltmarsh
2dc5f8a  sir-galahad  aws    preparing /Users/afarrell/projects/saltmarsh
cfb0009  sir-robin    aws    preparing /Users/afarrell/projects/saltmarsh
The above shows information about...[clipped]

$ vagrant status sir-robin
Current machine states:

sir-robin                 running (aws)

The EC2 instance is running. To stop this machine, you can run
`vagrant halt`. To destroy the machine, you can run `vagrant destroy`.

$ vagrant global-status
id       name         provider state     directory
-----------------------------------------------------------------------------
1b9c91d  arthur       aws    running   /Users/afarrell/projects/saltmarsh
824fc08  sir-lancelot aws    preparing /Users/afarrell/projects/saltmarsh
2dc5f8a  sir-galahad  aws    preparing /Users/afarrell/projects/saltmarsh
cfb0009  sir-robin    aws    running   /Users/afarrell/projects/saltmarsh

1 Answer 1

1

"preparing" is entered when the configuration is read and the VM is created, but the provider has not confirmed it to be "running". With virtualbox this is pretty quick and you usually never see that stage, but with remote instances the preparing stage might take some time.

BTW, if in doubt use the source: https://github.com/mitchellh/vagrant

1
  • That makes sense as far as it goes. What threw me off was, why would a vm be "preparing" right up until it gets asked its' status. Dec 3, 2015 at 19:54

Not the answer you're looking for? Browse other questions tagged .