Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

SOLVED:

The problem was that I had the http_proxy environment variable set. I then ran the keystone command line client with --debug and this what I saw.

# keystone --debug user-create --name admin --pass xxxx --email xxx@xxx
DEBUG:keystoneclient.session:REQ: curl -i -X POST http://cinnamon:35357/v2.0/users -H "User-Agent: python-keystoneclient" -H "Content-Type: application/json" -H "X-Auth-Token: xxxxx" -d '{"user": {"email": "xx@xxxx", "password": "xxx", "enabled": true, "name": "admin", "tenantId": null}}'
INFO:urllib3.connectionpool:Starting new HTTP connection (1): 8080
Unable to establish connection to http://cinnamon:35357/v2.0/users

Turns out the curl is trying to reach out through the :8080 port which is my proxy for external connections. So I set proxy to blank on the shell and it worked.

# export http_proxy=

However, this gives rise to 2 bugs that I am thinking of filing.

Bug 1: the python-keystoneclient does not show the "--debug" option on the command line when its run with "--help". This is a problem since this would have cut short by debgugging time by almost a day. I had to figure this out by going through the sources, not particularly efficient.

Bug 2: Handling the presence of the http_proxy varibale inside the python-keystoneclient. Maybe this is a bug that needs to be pushed to curl rather than python-keystoneclient.

SOLVED:

The problem was that I had the http_proxy environment variable set. I then ran the keystone command line client with --debug and this what I saw.

# keystone --debug user-create --name admin --pass xxxx --email xxx@xxx
DEBUG:keystoneclient.session:REQ: curl -i -X POST http://cinnamon:35357/v2.0/users -H "User-Agent: python-keystoneclient" -H "Content-Type: application/json" -H "X-Auth-Token: xxxxx" -d '{"user": {"email": "xx@xxxx", "password": "xxx", "enabled": true, "name": "admin", "tenantId": null}}'
INFO:urllib3.connectionpool:Starting new HTTP connection (1): 8080
Unable to establish connection to http://cinnamon:35357/v2.0/users

Turns out the curl is trying to reach out through the :8080 port which is my proxy for external connections. So I set proxy to blank on the shell and it worked.

# export http_proxy=

However, this gives rise to 2 bugs that I am thinking of filing.

Bug 1: the python-keystoneclient does not show the "--debug" option on the command line when its run with "--help". This is a problem since this would have cut short by debgugging time by almost a day. I had to figure this out by going through the sources, not particularly efficient.

Bug 2: Handling the presence of the http_proxy varibale inside the python-keystoneclient. Maybe this is a bug that needs to be pushed to curl rather than python-keystoneclient.

Update: Filed bug 1 https://bugs.launchpad.net/python-keystoneclient/+bug/1328813

SOLVED:

The problem was that I had the http_proxy environment variable set. I then ran the keystone command line client with --debug and this what I saw.

# keystone --debug user-create --name admin --pass xxxx --email xxx@xxx
DEBUG:keystoneclient.session:REQ: curl -i -X POST http://cinnamon:35357/v2.0/users -H "User-Agent: python-keystoneclient" -H "Content-Type: application/json" -H "X-Auth-Token: xxxxx" -d '{"user": {"email": "xx@xxxx", "password": "xxx", "enabled": true, "name": "admin", "tenantId": null}}'
INFO:urllib3.connectionpool:Starting new HTTP connection (1): 8080
Unable to establish connection to http://cinnamon:35357/v2.0/users

Turns out the curl is trying to reach out through the :8080 port which is my proxy for external connections. So I set proxy to blank on the shell and it worked.

# export http_proxy=

However, this gives rise to 2 bugs that I am thinking of filing.

Bug 1: the python-keystoneclient does not show the "--debug" option on the command line when its run with "--help". This is a problem since this would have cut short by debgugging time by almost a day. I had to figure this out by going through the sources, not particularly efficient.

Bug 2: Handling the presence of the http_proxy varibale inside the python-keystoneclient. Maybe this is a bug that needs to be pushed to curl rather than python-keystoneclient.

Update: Filed bug 1 https://bugs.launchpad.net/python-keystoneclient/+bug/1328813

https://bugs.launchpad.net/python-keystoneclient/+bug/1328813 Update': Filed bug 2 https://bugs.launchpad.net/python-keystoneclient/+bug/1328837

SOLVED:

The problem was that I had the http_proxy environment variable set. I then ran the keystone command line client with --debug and this what I saw.

# keystone --debug user-create --name admin --pass xxxx --email xxx@xxx
DEBUG:keystoneclient.session:REQ: curl -i -X POST http://cinnamon:35357/v2.0/users -H "User-Agent: python-keystoneclient" -H "Content-Type: application/json" -H "X-Auth-Token: xxxxx" -d '{"user": {"email": "xx@xxxx", "password": "xxx", "enabled": true, "name": "admin", "tenantId": null}}'
INFO:urllib3.connectionpool:Starting new HTTP connection (1): 8080
Unable to establish connection to http://cinnamon:35357/v2.0/users

Turns out the curl is trying to reach out through the :8080 port which is my proxy for external connections. So I set proxy to blank on the shell and it worked.

# export http_proxy=

However, this gives rise to 2 bugs that I am thinking of filing.

Bug 1: the python-keystoneclient does not show the "--debug" option on the command line when its run with "--help". This is a problem since this would have cut short by debgugging time by almost a day. I had to figure this out by going through the sources, not particularly efficient.

Bug 2: Handling the presence of the http_proxy varibale inside the python-keystoneclient. Maybe this is a bug that needs to be pushed to curl rather than python-keystoneclient.

Update: Filed bug 1 https://bugs.launchpad.net/python-keystoneclient/+bug/1328813 Update': https://bugs.launchpad.net/python-keystoneclient/+bug/1328813

Update: Filed bug 2 https://bugs.launchpad.net/python-keystoneclient/+bug/1328837