glance-manage ignores --sql_connection parameter and uses connection from config file /etc/glance/glance-registry.conf . CLI parameter should override setting from config file.
[para@virtual-rhel packstack]$ sudo glance-manage --sql_connection="mysql://glance:4437d490c3cf4c50@192.168.122.71/glance" db_sync
2013-05-02 13:52:52.543 13954 CRITICAL glance [-] (OperationalError) (2002, "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)") None None
[para@virtual-rhel packstack]$ mysql -h 192.168.122.71 -u'glance' -p'4437d490c3cf4c50' glance
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 165
Server version: 5.1.66 Source distribution
Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql>
Unfortunately, this is not a bug. Oslo currently gives priority to config files instead of cli arguments, which is the expected behavior. I started a discussion on the m-l proposing to invert this behavior.
http://