Open maishsk opened 11 years ago
yep same problem, did you find resolution?
vagrant destroy will stop the rackspace server
@maishsk Sorry about the delay in the reply!
I don't know how feasible implementing halt
is. You can't just stop a VM and then resume it's execution later. The close thing we could do is, take an image of that VM and then delete it. This unfortunately would be slow and it wouldn't retain the IP either.
@deanmalmgren suggested adding a better help message to indicate this. I will have to add it to the list!
It appears that there isn't an equivalent way to halt a Rackspace server at this time [upvote feature request here]. I would suggest having a more user-friendly error message, perhaps something like
The 'halt' action does not work with the Rackspace API at this time. Upvote the feature request if this is something you want http://bit.ly/H5xND1. In the meantime, the 'destroy' action can be used to stop and permanently remove the Rackspace server.
Edit at will. It just seems like it would be better to alert the user that it is a Rackspace issue, not a vagrant-rackspace issue and provide a workaround in the interim. Thoughts @krames?
I'd implement this myself but I can't seem to figure out how to do it (vagrant/ruby n00b).
@deanmalmgren seems reasonable to me. Let me see if I can't squeeze it in next week.
When running vagrant halt the following is displayed
C:\VM\rackspace>vagrant halt Vagrant attempted to call the action 'halt' on the provider 'RackSpace Cloud', 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.