Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Whenvagrant reload an existing but stoped machine it does not start #57

Closed
ggiamarchi opened this issue Jun 27, 2014 · 1 comment
Closed

Whenvagrant reload an existing but stoped machine it does not start #57

ggiamarchi opened this issue Jun 27, 2014 · 1 comment
Assignees
@julienvey
Labels
bug
Milestone
0.3

Comments

@ggiamarchi
Copy link
Owner

Vagrant stops on this nova error

{"conflictingRequest": {"message": "Instance a34b04df-0b36-422f-8425-5a1b6998085a in vm_state stopped. Cannot stop while the instance is in this state.", "code": 409}}

Is it the normal behavior ?
@julienvey
Copy link
Collaborator

no, it should just up

@julienvey julienvey added bug and removed question labels Jul 1, 2014
@ggiamarchi ggiamarchi added this to the 0.3 milestone Jul 8, 2014
@julienvey julienvey self-assigned this Aug 22, 2014
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jan 18, 2016
@julienvey
vagrant up works with different machine states
146c7db 
Fix ggiamarchi#57 ggiamarchi#56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@julienvey julienvey

Labels
bug
Projects
None yet
Milestone
0.3
Development

No branches or pull requests
2 participants
@julienvey @ggiamarchi