-
Notifications
You must be signed in to change notification settings - Fork 102
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
Network api URL resolve from keystone catalog is not working #49
Comments
ggiamarchi
added a commit
that referenced
this issue
Aug 2, 2014
Closed
ggiamarchi
added a commit
that referenced
this issue
Aug 2, 2014
ggiamarchi
added a commit
that referenced
this issue
Aug 2, 2014
Merged
Sharpie
pushed a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Jan 18, 2016
Sharpie
pushed a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Jan 18, 2016
Sharpie
pushed a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Jan 18, 2016
Sharpie
pushed a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Jan 18, 2016
Sharpie
pushed a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Jan 18, 2016
Merge ggiamarchi#49 looks good
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
URL from catalog is something like http://neutronUrl/ and the plugin use it without any modification. Actually, the URL must be ended with the API version (something like http://neutronUrl/v2.0).
To get the real URL we must GET http://neutronUrl/ and parse the response body.
As a workaround, always set value for openstack_network_url provider's property.
The text was updated successfully, but these errors were encountered: