Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Operators

keystone-manage problem!!!

 

 

OpenStack operators RSS feed   Index | Next | Previous | View Threaded


sacampa at gmv

Apr 18, 2012, 5:00 AM

Post #1 of 5 (3277 views)
Permalink
keystone-manage problem!!!

Hi:

Firt of all thanks is advance :)

I´m trying to install Nova, Glance and Keystone. I´m using this guide http://uksysadmin.wordpress.com/2012/03/28/screencast-video-of-an-install-of-openstack-essex-on-ubuntu-12-04-under-virtualbox/
which includes some scripts to make esasier the installation process.

My keystone configuration file is /etc/keystone/keystone.conf and it has the field : connection = mysql://keystone:openstack [at] 192/keystone



My problem is when I try to sync keystone whith my MySQL database by: keystone-manage db_sync

It seems like something with Python.



This is the output of keystone-manage db_sync:


Traceback (most recent call last):
File "/usr/bin/keystone-manage", line 28, in <module>
cli.main(argv=sys.argv, config_files=config_files)
File "/usr/lib/python2.7/dist-packages/keystone/cli.py", line 148, in main
return run(cmd, (args[:1] + args[2:]))
File "/usr/lib/python2.7/dist-packages/keystone/cli.py", line 134, in run
return CMDS[cmd](argv=args).run()
File "/usr/lib/python2.7/dist-packages/keystone/cli.py", line 36, in run
return self.main()
File "/usr/lib/python2.7/dist-packages/keystone/cli.py", line 57, in main
driver.db_sync()
File "/usr/lib/python2.7/dist-packages/keystone/identity/backends/sql.py", line 135, in db_sync
migration.db_sync()
File "/usr/lib/python2.7/dist-packages/keystone/common/sql/migration.py", line 50, in db_sync
current_version = db_version()
File "/usr/lib/python2.7/dist-packages/keystone/common/sql/migration.py", line 66, in db_version
return db_version_control(0)
File "/usr/lib/python2.7/dist-packages/keystone/common/sql/migration.py", line 72, in db_version_control
CONF.sql.connection, repo_path, version)
File "<string>", line 2, in version_control
File "/usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py", line 159, in with_engine
return f(*a, **kw)
File "/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 250, in version_control
ControlledSchema.create(engine, repository, version)
File "/usr/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 139, in create
table = cls._create_table_version(engine, repository, version)
File "/usr/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 180, in _create_table_version
if not table.exists():
File "/usr/lib/python2.7/dist-packages/sqlalchemy/schema.py", line 549, in exists
self.name, schema=self.schema)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2274, in run_callable
conn = self.contextual_connect()
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2340, in contextual_connect
self.pool.connect(),
File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 210, in connect
return _ConnectionFairy(self).checkout()
File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 371, in __init__
rec = self._connection_record = pool._do_get()
File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 697, in _do_get
con = self._create_connection()
File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 174, in _create_connection
return _ConnectionRecord(self)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 256, in __init__
self.connection = self.__connect()
File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 316, in __connect
connection = self.__pool._creator()
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/strategies.py", line 80, in connect
return dialect.connect(*cargs, **cparams)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 280, in connect
return self.dbapi.connect(*cargs, **cparams)
File "/usr/lib/python2.7/dist-packages/MySQLdb/__init__.py", line 81, in Connect
return Connection(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 187, in __init__
super(Connection, self).__init__(*args, **kwargs2)
sqlalchemy.exc.OperationalError: (OperationalError) (1045, "Access denied for user '<mailto:'keystone'@'opst1'>keystone'@'opst1'<mailto:'keystone'@'opst1'> (using password: YES)") None None



Sergio Ariel
de la Campa Saiz
GMV-SES Infraestructura /
GMV-SES Infrastructure





GMV
Isaac Newton, 11
P.T.M. Tres Cantos
E-28760 Madrid
Tel.
+34 91 807 21 00
Fax
+34 91 807 21 99
www.gmv.com







______________________
This message including any attachments may contain confidential
information, according to our Information Security Management System,
and intended solely for a specific individual to whom they are addressed.
Any unauthorised copy, disclosure or distribution of this message
is strictly forbidden. If you have received this transmission in error,
please notify the sender immediately and delete it.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
puede contener informacion clasificada por su emisor como confidencial
en el marco de su Sistema de Gestion de Seguridad de la
Informacion siendo para uso exclusivo del destinatario, quedando
prohibida su divulgacion copia o distribucion a terceros sin la
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje
erroneamente, se ruega lo notifique al remitente y proceda a su borrado.
Gracias por su colaboracion.

______________________


berendt at b1-systems

Apr 18, 2012, 5:06 AM

Post #2 of 5 (3230 views)
Permalink
Re: keystone-manage problem!!! [In reply to]

Hello Sergio.

On 04/18/2012 02:00 PM, Sergio Ariel de la Campa Saiz wrote:
> sqlalchemy.exc.OperationalError: (OperationalError) (1045,
> "Access denied for user'
> <mailto:%27keystone%27@%27opst1%27>keystone'@'opst1'
> <mailto:%27keystone%27@%27opst1%27> (usingpassword: YES)") NoneNone

You don't have the permissions to access your created database with the
specified credentials in your keystone configuration.

How have you created the database on your MySQL server? Have you checked
that you can login from the system where you're running the keystone
service to the MySQL database?

HTH, Christian.

--
Christian Berendt
Solution Architect
Mail: berendt [at] b1-systems

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


sacampa at gmv

Apr 18, 2012, 6:40 AM

Post #3 of 5 (3229 views)
Permalink
Re: keystone-manage problem!!! [In reply to]

Hi :-)
Thank for you pay attention to my problem.
This is the way I created the database

mysql -uroot -pPASS -e "CREATE DATABASE keystone;"
mysql -uroot -pPASS -e "SET PASSWORD FOR 'keystone'@'%'= PASSWORD('PASS');"
mysql -uroot -pPASS -e "GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'%' WITH GRANT OPTION;"

I have already try to connect to MySQL and I can see keystone database, I mean, the database is created without problem.

Gretings...


Sergio Ariel
de la Campa Saiz
GMV-SES Infraestructura /
GMV-SES Infrastructure

GMV
Isaac Newton, 11
P.T.M. Tres Cantos
E-28760 Madrid
Tel.
+34 91 807 21 00
Fax
+34 91 807 21 99
www.gmv.com
________________________________________
De: openstack-operators-bounces [at] lists [openstack-operators-bounces [at] lists] En nombre de Christian Berendt [berendt [at] b1-systems]
Enviado el: miércoles, 18 de abril de 2012 14:06
Para: openstack-operators [at] lists
Asunto: Re: [Openstack-operators] keystone-manage problem!!!

Hello Sergio.

On 04/18/2012 02:00 PM, Sergio Ariel de la Campa Saiz wrote:
> sqlalchemy.exc.OperationalError: (OperationalError) (1045,
> "Access denied for user'
> <mailto:%27keystone%27@%27opst1%27>keystone'@'opst1'
> <mailto:%27keystone%27@%27opst1%27> (usingpassword: YES)") NoneNone

You don't have the permissions to access your created database with the
specified credentials in your keystone configuration.

How have you created the database on your MySQL server? Have you checked
that you can login from the system where you're running the keystone
service to the MySQL database?

HTH, Christian.

--
Christian Berendt
Solution Architect
Mail: berendt [at] b1-systems

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
______________________
This message including any attachments may contain confidential
information, according to our Information Security Management System,
and intended solely for a specific individual to whom they are addressed.
Any unauthorised copy, disclosure or distribution of this message
is strictly forbidden. If you have received this transmission in error,
please notify the sender immediately and delete it.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
puede contener informacion clasificada por su emisor como confidencial
en el marco de su Sistema de Gestion de Seguridad de la
Informacion siendo para uso exclusivo del destinatario, quedando
prohibida su divulgacion copia o distribucion a terceros sin la
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje
erroneamente, se ruega lo notifique al remitente y proceda a su borrado.
Gracias por su colaboracion.

______________________

_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


berendt at b1-systems

Apr 18, 2012, 6:47 AM

Post #4 of 5 (3235 views)
Permalink
Re: keystone-manage problem!!! [In reply to]

On 04/18/2012 03:40 PM, Sergio Ariel de la Campa Saiz wrote:
> mysql -uroot -pPASS -e "CREATE DATABASE keystone;"
> mysql -uroot -pPASS -e "SET PASSWORD FOR 'keystone'@'%'= PASSWORD('PASS');"
> mysql -uroot -pPASS -e "GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'%' WITH GRANT OPTION;"
>
> I have already try to connect to MySQL and I can see keystone database, I mean, the database is created without problem.

mysql://keystone:openstack [at] 192/keystone

Try to connect to the MySQL database using the IP address as used in
your keystone.conf and do this from the system where you want to start
keystone. If this is possible there should be no problems.

Are you sure that "openstack" is the right password when you used "PASS"
during the creation of the database?

Regards, Christian.

--
Christian Berendt
Solution Architect
Mail: berendt [at] b1-systems

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


sacampa at gmv

Apr 20, 2012, 1:02 AM

Post #5 of 5 (3242 views)
Permalink
Re: keystone-manage problem!!! [In reply to]

Hi Christian:

Thanks a lot for your help!!! I did not write you before because I was deep inside my installation and configuration process :-)
Sorry for bothering you but now i have a problem with VNC. This is what I have in my nova.conf file
--vncserver_host=0.0.0.0
--vncproxy_url=http://192.168.111.51:6080

(192.168.111.51 is my public IP for the Ubuntu server in wich nova runs.)

I have installed nova-vncproxy package and started it, but when I try to connect to an instance using dashboard, I get this message:
"VNC console is currently unavailabe. Please try again later"


Once again, thanks a lot and sorry for bothering you.

Sergio Ariel
de la Campa Saiz
GMV-SES Infraestructura /
GMV-SES Infrastructure

GMV
Isaac Newton, 11
P.T.M. Tres Cantos
E-28760 Madrid
Tel.
+34 91 807 21 00
Fax
+34 91 807 21 99
www.gmv.com
________________________________________
De: Christian Berendt [berendt [at] b1-systems]
Enviado el: miércoles, 18 de abril de 2012 15:47
Para: Sergio Ariel de la Campa Saiz
CC: openstack-operators [at] lists
Asunto: Re: [Openstack-operators] keystone-manage problem!!!

On 04/18/2012 03:40 PM, Sergio Ariel de la Campa Saiz wrote:
> mysql -uroot -pPASS -e "CREATE DATABASE keystone;"
> mysql -uroot -pPASS -e "SET PASSWORD FOR 'keystone'@'%'= PASSWORD('PASS');"
> mysql -uroot -pPASS -e "GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'%' WITH GRANT OPTION;"
>
> I have already try to connect to MySQL and I can see keystone database, I mean, the database is created without problem.

mysql://keystone:openstack [at] 192/keystone

Try to connect to the MySQL database using the IP address as used in
your keystone.conf and do this from the system where you want to start
keystone. If this is possible there should be no problems.

Are you sure that "openstack" is the right password when you used "PASS"
during the creation of the database?

Regards, Christian.

--
Christian Berendt
Solution Architect
Mail: berendt [at] b1-systems

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
______________________
This message including any attachments may contain confidential
information, according to our Information Security Management System,
and intended solely for a specific individual to whom they are addressed.
Any unauthorised copy, disclosure or distribution of this message
is strictly forbidden. If you have received this transmission in error,
please notify the sender immediately and delete it.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
puede contener informacion clasificada por su emisor como confidencial
en el marco de su Sistema de Gestion de Seguridad de la
Informacion siendo para uso exclusivo del destinatario, quedando
prohibida su divulgacion copia o distribucion a terceros sin la
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje
erroneamente, se ruega lo notifique al remitente y proceda a su borrado.
Gracias por su colaboracion.

______________________

_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

OpenStack operators RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.