Ask Your Question

ghebda's profile - activity

2015-11-10 10:48:01 -0500 received badge  Good Answer (source)
2015-09-29 12:09:20 -0500 received badge  Nice Answer (source)
2015-09-22 02:33:57 -0500 received badge  Nice Answer (source)
2015-05-15 08:07:53 -0500 commented answer I am getting an authentication exception while creating an user in Openstack Kilo version

I am putting another update in my answer, since I have some new info on the keystone-manage token_flush issue.

2015-05-15 08:05:17 -0500 received badge  Enthusiast
2015-05-14 13:09:42 -0500 commented answer I am getting an authentication exception while creating an user in Openstack Kilo version

Yeah, that should work. Did you replace controller with the IP of your controller node in the keystone.conf database connection line and try again? If so, how did it go?

2015-05-14 08:54:34 -0500 commented question I am getting an authentication exception while creating an user in Openstack Kilo version

Again, see answer update. Need more characters.

2015-05-14 04:34:06 -0500 received badge  Teacher (source)
2015-05-13 15:38:47 -0500 commented question I am getting an authentication exception while creating an user in Openstack Kilo version

Also, I don't know if token_flush not working is intended, a bug, or a configuration problem that I also have. According to this link, it looks like they intended to have it in Kilo: http://docs.openstack.org/developer/keystone/configuration.html (http://docs.openstack.org/developer/k...) I haven't found anything on that problem yet...

2015-05-13 15:22:21 -0500 commented question I am getting an authentication exception while creating an user in Openstack Kilo version

See my updated, answer. I think I'm going to need more characters.

2015-05-13 11:03:40 -0500 commented question ERROR: openstack 'Namespace' object has no attribute 'os_url'

Can you run the openstack service create with a --debug flag and add the output to your question? Also, any information that gets printed to /var/log/keystone/keystone.log or keystone-all.log would give a little more information about what exactly is failing.

2015-05-12 15:07:38 -0500 commented question I am getting an authentication exception while creating an user in Openstack Kilo version

Can you provide the contents of your /etc/keystone/keystone.conf file as well any log output from /var/log/keystone/keystone.log and /var/log/keystone/keystone-all.log from the time when you are running the openstack-service-create? Thanks.

2015-05-12 14:50:07 -0500 commented question ERROR: openstack 'Namespace' object has no attribute 'os_url'

After you run export OS_URL=http://controller:35357/v2.0, can you run

 # printenv | grep OS_URL

It sounds like that environment variable isn't getting set. You should also be able to run openstack service create with an --os-url flag and get the same results as setting the env variable.

2015-05-12 14:32:27 -0500 answered a question Horizon 500 Error (no module named angular_cookies)

Run:

 pip install XStatic-Angular-Cookies

It's complaining about a module you don't have. This should fix it.

2015-05-12 08:15:23 -0500 commented answer nova service-list fails with ERROR (Unauthorized): Unauthorized (HTTP 401)

Hi. I solved why my install was giving me that 401 error and updated my post above. It was a discrepancy between what's in the Kilo installation guide and actual valid lines in the INI files. If you haven't solved it yet, maybe try that.

2015-05-11 09:24:32 -0500 received badge  Editor (source)
2015-05-11 09:03:23 -0500 answered a question I am getting an authentication exception while creating an user in Openstack Kilo version

[UPDATE 3]

Can you run a yum list installed | grep openstack and check which packages actually downloaded? It turns out if you jumped on the Kilo release on day 1, like I did, they had both kilo and juno repos in the /etc/yum.repos.d/rdo-release.repo. Then, they moved the location of the kilo repos, so about half the packages I ended up downloading came from the juno repo. I wonder if they did something similar with the the sources in the Ubuntu release. It was causing all sorts of weird little buggy things, including the keystone-manage token_flush problem I was having. They have since release an updated version with no juno repo and the correct url for the kilo repo.

[UPDATE 2]

If you do an nslookup controller, does it resolve to an IP address? The reason I ask is that the hostname of your controller node looks like it is XXX-XX-156, and the @controller part of the database connection line is looking for whatever hostname you assign to your controller. It has to be resolvable by your dns and/or (preferrably and) your /etc/hosts file. Right now, I'm sort of looking for any part of the config that might be off, and since I don't know your environment, that one sticks out to me as a potential problem.

[UPDATE] From the logs, it looks like something is trying to call the same function that running keystone-manage token_flush does. I have what appears to be a functioning keystone setup and I get that same traceback when I run keystone-manage token_flush by hand:

[root@kilocontroller ~]# keystone-manage token_flush
2015-05-13 15:11:20.412 32368 INFO keystone.common.kvs.core [-] Using default dogpile sha1_mangle_key as KVS region token-driver key_mangler
2015-05-13 15:11:20.413 32368 CRITICAL keystone [-] NotImplemented: The action you have requested has not been implemented.
2015-05-13 15:11:20.413 32368 TRACE keystone Traceback (most recent call last):
2015-05-13 15:11:20.413 32368 TRACE keystone   File "/usr/bin/keystone-manage", line 44, in <module>
2015-05-13 15:11:20.413 32368 TRACE keystone     cli.main(argv=sys.argv, config_files=config_files)
2015-05-13 15:11:20.413 32368 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/cli.py", line 306, in main
2015-05-13 15:11:20.413 32368 TRACE keystone     CONF.command.cmd_class.main()
2015-05-13 15:11:20.413 32368 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/cli.py", line 175, in main
2015-05-13 15:11:20.413 32368 TRACE keystone     token_manager.driver.flush_expired_tokens()
2015-05-13 15:11:20.413 32368 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/token/persistence/backends/kvs.py", line 356, in flush_expired_tokens
2015-05-13 15:11:20.413 32368 TRACE keystone     raise exception.NotImplemented()
2015-05-13 15:11:20.413 32368 TRACE keystone NotImplemented: The action you have requested has not been implemented.
2015-05-13 15:11:20.413 32368 TRACE keystone

If I were you I would double check any options in keystone.conf that deal with tokens. Did you follow ... (more)

2015-05-07 15:14:34 -0500 answered a question nova service-list fails with ERROR (Unauthorized): Unauthorized (HTTP 401)

[UPDATE] I have solved the problem I was having (see details below). For me, the new settings that I followed in [keystone_authtoken] in both nova.conf and glance-api.conf from the Kilo installation guide were the problem. I checked out the Kilo configuration guide, and I'm not even seeing project_domain_id, user_domain_id, project_name, username, and password as valid entries. I had to make a few changes:

  1. The auth_uri should be the full URL, including version number
  2. user admin_tenant_name, admin_user, and admin_password.

So my new [keystone_authtoken] section looks like this:

[keystone_authtoken]
auth_uri = http://kilocontroller:5000/v2.0
identity_uri = http://kilocontroller:35357
admin_tenant_name = service
admin_user = nova
admin_password = XXXXXXXXXXXX

I made the same changes in my glance-api.conf file and now I can do an image-list and image create, so I'm happy.

adendukuri, can you see if this is the source of your error messages as well?

[ORIGINAL POST BELOW:]

I'm working on a Kilo installation, and it looks like I'm having the same trouble with the nova and glance APIs.

I followed the Kilo installation guide for the config files and set up the keystone_authtoken section as follows:

[keystone_authtoken]
auth_uri = http://kilocontroller:5000
identity_uri = http://kilocontroller:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = nova
password = XXXXXXXXXXX

And before I run these commands, I source the admin credentials. That also uses the suggested environment variables from the Kilo installation guide:

[root@kilocontroller ~]# cat admin-openrc.sh 
export OS_PROJECT_DOMAIN_ID=default
export OS_USER_DOMAIN_ID=default
export OS_PROJECT_NAME=admin
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=XXXXXXXXXXXXXXX
export OS_AUTH_URL=http://kilocontroller:35357/v3
export OS_IMAGE_API_VERSION=2

I get the same error in my logs:

[root@kilocontroller ~]# tail -4 /var/log/nova/nova-api.log
2015-05-07 09:04:06.276 3302 ERROR keystonemiddleware.auth_token [-] Bad response code while validating token: 400
2015-05-07 09:04:06.277 3302 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Expecting to find username or userId in passwordCredentials - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}
2015-05-07 09:04:06.277 3302 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2015-05-07 09:04:06.278 3302 INFO nova.osapi_compute.wsgi.server [-] 192.168.10.110 "GET /v2/3a5e3f78fcbf43c9b36930a8943bc735/os-services HTTP/1.1" status: 401 len: 284 time: 0.0119960

I also ran the above curl command, and it looks like it is successful:

[root@kilocontroller ~]# curl -s -X POST http://kilocontroller:5000/v2.0/tokens \
-H "Content-Type: application/json" \
 -d '{"auth": {"tenantName": "'"$OS_TENANT_NAME"'", "passwordCredentials":
 {"username": "'"$OS_USERNAME"'", "password": "'"$OS_PASSWORD"'"}}}'
 {"access": {"token": {"issued_at": "2015-05-07T14:39:04.401974", "expires": "2015-05-07T15:39:04Z", "id": "e5807245d39c46ed84ac2bfe5b72ea8e", "tenant": {"description": "Admin Project", "enabled": true, "id": "3a5e3f78fcbf43c9b36930a8943bc735", "name": "admin"}, "audit_ids": ["MCDVi8YATQOrDDf2xFX7Pg"]}, "serviceCatalog": [{"endpoints": [{"adminURL": "http://kilocontroller:9292", "region": "RegionOne", "internalURL": "http://kilocontroller:9292", "id": "7c23f97f2bdc45268f898f98d1f5609e", "publicURL": "http://kilocontroller:9292"}], "endpoints_links": [], "type": "image", "name": "glance"}, {"endpoints": [{"adminURL": "http://kilocontroller:8774/v2/3a5e3f78fcbf43c9b36930a8943bc735", "region": "RegionOne", "internalURL": "http://kilocontroller:8774/v2/3a5e3f78fcbf43c9b36930a8943bc735", "id": "2258953915fb4a4ca352f0914ad29136", "publicURL": "http://kilocontroller:8774/v2/3a5e3f78fcbf43c9b36930a8943bc735 ...
(more)