-
Notifications
You must be signed in to change notification settings - Fork 101
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.
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
unknown error on simple VM start #193
Comments
In your Vagrantfile the network configuration is wrong. The attribute os.networks = ['net04'] or using the os.networks << 'net04' I guess in that situation we should just print a clear error message instead of this dirty crash. Furthermore, at the end of your log, after the text message you should have seen an exception backtrace with an error message that looks like
Can you please tell me if you just forgot to copy/paste this trace from your log or if you don't have it at all ? |
Actually, i think we should accept a single value instead of failing. It would be equal to an array of size one. |
I do not have that 'Catched Error: ...' message at all, as far as I can Waow -- apres la correction propose, ca marche! Merci beaucoup pour la On Wed, Jan 14, 2015 at 7:19 PM, Guillaume Giamarchi <
John Jainschigg, MCA (200 - Professional) |
A few questions to try to reproduce your problem :
|
Plugin: 0.6.0 (November 28, 2014) When I replace the network config with os.networks = ['net04'] doing Bringing machine 'default' up with 'openstack' provider... On Wed, Jan 14, 2015 at 8:03 PM, Guillaume Giamarchi <
John Jainschigg, MCA (200 - Professional) |
Ok great. We keep this issue open to make |
I'm trying to launch a plain vanilla VM on my (hosted) OpenStack, using the example_box metadata.js, tar'd into openstack.box. When I submit the following Vagrantfile (only relevant content shown):
... the provider tells me that multiple networks were found, and I should use a network ID to disambiguate. Doing so does not fix the problem.
When I remove the equate for os.floating_ip_pool (presumably this means 'don't assign a floating IP to this server') and try vagrant up --provider=openstack again, I get an unknown error with the following log:
Obviously, it's authenticating okay, it's getting the service catalog, flavor list, and perhaps even the network list, but then breaking. Thoughts?
The text was updated successfully, but these errors were encountered: