Glance Commands: Invalid Credentials [closed]
Ok, so before I punch a hole into my laptop, let me open up a question for you all... I'll try to provide as much background, up front to prevent a long dialogue. I'm trying to run Openstack on one single device. I have keystone installed, and it's running fine. I can get tokens, add services, tenants, users etc... I went to install and configure glance, and it's giving me a ton of issues. I'm running Opensuse 13.1, trying to install the juno series of openstack.
I installed glance successfully, and configured the glance-api and glance-registry conf files according to the documentation. But everytime I run any glance based command such as ' glance index ' or ' glance image-list ' Basically any glance based command will give me the same error. So I can't create any images. Now before you jump to assume it's a username/password issue, let me give you the full logs and errors.
Ok so first off these are my environment variables:
OS_AUTH_URL="http://127.0.0.1:5000/v2.0"
OS_PASSWORD="<passwordforadmin>"
OS_TENANT_NAME="admin"
OS_USERNAME="admin"
My api / registry configs are pretty much mirrors of the auth_token section
This is the /etc/glance/glance-api.conf
[keystone_authtoken]
#auth_host = 127.0.0.1
#auth_port = 35357
#auth_protocol = http
auth_uri = http://localhost:5000/v2.0
identity_uri = http://localhost:35357
admin_tenant_name = service
admin_user = admin
admin_password = <passwordforglance>
Note which ones are commented out and which ones are active
Below is my /etc/glance/glance-registry.conf
[keystone_authtoken]
#auth_host = 127.0.0.1
#auth_port = 35357
#auth_protocol = http
identity_uri = http://localhost:35357
auth_uri = http://localhost:5000/v2.0
admin_tenant_name = service
admin_user = glance
admin_password = <passwordforglance>
Please note which ones are commented out and the the passwords, which differ from the environment variable. Hopefully it's correct so far.
Ok, so let's move onto a big question... in the documentation for Juno it says that the connection = mysql statement should be under the [database] header. Well the problem with that....is that there is NO [database] header. In both glance-api.conf and glance-registry.conf there is a [sql] header. Should I put my connection = mysql:// in the [sql] section, or create the [database] header and put the connection statement in there?
here's what my file looks like:
[sql]
connection = mysql://glance:csc3gadm@localhost/glance
#connection = sqlite:////var/lib/glance/glance.db
Note that I commented out the previous connection. Should I do this? Or should I add the connection = mysql:// and leave the connection = sqlite statement in as well?
Okay, so there's also the following error...whenever I try to do a glance db_sync, it sends and creates a file called. /var/lib/glance/glance.sqlite Should this happened? There is NOTHING inside the mysql glance table. But yet my glance confs have all of the default sqlite statements, commented out. How is this still happening? On both conf files i have my mysql commands set, yet it doesn't seem to matter.
So finally my main question ...
The problem with respect to the above problem was, Mr. Steven unknowingly downloaded Havana packages and started configuring OpenStack with Juno installation guide