precise glance-client --insecure option doesn't work

[Brad Marshall]

The version of glance-client in precise doesn't handle --insecure or -k correctly, as follows:

$ dpkg-query -W glance-client
glance-client 2012.1.3+stable~20120821-120fcf-0ubuntu1
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Codename: precise

$ glance --version
glance 2012.1.3-dev
$ glance -k -v -N https://ip.ad.dr.es:5000/v2.0 -I glanceUser -K thisisnotmypassword -T tenant -S keystone --ssl index
Failed to show index. Got error:
Connect error/bad request to Auth service at URL https://ip.ad.dr.es:5000/v2.0/tokens.
Completed in 0.0234 sec.

With a locally installed version of the glance client for testing:

$ /path/to/new/glance/bin/glance --version
glance 2012.2-dev
$ /path/to/new/glance/bin/glance -k -v -N https://ip.ad.dr.es:5000/v2.0 -I glanceUser -K thisisnotmypassword -T tenant -S keystone --ssl index
ID Name Disk Format Container Format Size
------------------------------------ ------------------------------ -------------------- -------------------- --------------
192d0133-38f0-e32d-bf3a-aae680da62d3 test upload None None 0
a2303a68-147f-7182b-369c-89230f47c6db test upload None None 0
Completed in 0.1911 sec.

[James Page (james-page)]

I'm wondering whether this is a difference in handling of SSL protocols; the Folsom version of the glance client uses curl under the hood whereas 2012.1 uses python/ssl+openssl under the hood.

[James Page (james-page)]

Hmm - OK - I see; the code that performs the authentication against keystone is not using the insecure flag hence the problem

[James Page (james-page)]

Line 264 of common/auth.py for reference.

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release