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
openstack auth with nova driver #36548
Comments
Hi @abonillasuse - Thanks for filing this issue. I am a little bit unsure of how you're setting up your configuration. I do see that you do have The failure you listed comes from this line which calls out to this cloud function and produces the error. Though since you have I am not as familiar with the nova driver and module, but I bet @gtmanfred can help out on this one. What are we missing here? |
@gtmanfred do you have any idea why this could be failing? I've used the nova driver settings that are required but I still can't authenticate. Is there a guide or correct document I should be looking at? Update: Using worked for me. Perhaps Keystone/API v 3 is not supported yet? |
I am going to look at this on monday, tagging myself with it so I don't forget. |
@gtmanfred Any news from this? |
@abonillasuse can you remove the /auth/tokens from the identity_url. That is one difference between nova and openstack drivers, for the openstack driver you need to add the auth/tokens or /tokens for v2, but for nova, it should use the auth version and add the correct thing to the end (the novaclient and libcloud drivers require different identity urls) |
Hi. I have the same problem Setup
Log are [ here ] https://gist.github.com/akhmetgali/a1ebd8dbcb3b0976f74056badb688164 |
I have been able to replicate this issue, and it definitely appears to be caused by mitaka moving to defaulting on keystone 3. There appears to be a problem that we can't set the project_domain_name and user_domain_name yet. |
So, this would have worked if novaclient was sanely written, instead it is not, and they dropped really using client.Client() as the authentication portion. So it does not support keystonev3. Now, the shell command from novaclient does support keystonev3, because the shell builds it's own session and passes it to the client.Client() class. so we are going to have to do that, and that should make this work for yall :) I will try and finish it by the end of the week |
I can use v2 with Liberty. But the driver still is not happy. I was able to set things up with the openstack driver with v2. @gtmanfred can you share the config you used with the nova driver? (since I guess nova is the latest driver...) |
it is worth noting that if you are using mitaka, you can set
in /etc/keystone/keystone.conf and use the v2 identity to authenticate. I am still working on getting the catalog to render correctly though. |
Can someone try out these two commits and see if they work for you? you should only have to add If it is not default, also add
under the profile, like you do in your environment scripts from setting up openstack. |
Sorry, here is the commits 2016.3...gtmanfred:nova |
Hi! I'm trying to do with new commits but it's fail
|
Please include your provider config
|
my provider config my-os: |
Use 'project_domain_id' and 'user_domain_id' like openstack client and Also, novaclient adds the /auth/tokens, so remove that from your auth_url
|
Sorry, it should be project_domain_name and user_domain_name
|
Description of Issue/Question
I'm unable to connect to my openstack setup, there might be a config line missing.
Setup
I tried following
https://docs.saltstack.com/en/2015.8/ref/clouds/all/salt.cloud.clouds.nova.html
but using the keystone.user config fails
because it wants the older settings as documented on the openstack driver
https://docs.saltstack.com/en/latest/topics/cloud/config.html#openstack
(I know nova and openstack are separate drivers)
Steps to Reproduce Issue
Versions Report
The text was updated successfully, but these errors were encountered: