| 2015-07-03 12:28:39 |
Vadim Rovachev |
description |
If we use http proxy ip like a glance endpoint and add metadata for image in bug: https://bugs.launchpad.net/horizon/+bug/1449260
then http response have wrong HTTP type.
reproduced on branch: stable/juno
Steps to reproduce:
Precondition steps:
httpproxy glance endpoint: http://192.168.0.2:9292
host ip with runned glance-api: 192.168.0.6
Step 1. Create glance image, e.g.:
glance image-create --name test --id <uuid> --disk-format qcow2 --container-format bare --file <file>
response: http://paste.openstack.org/show/338516/
Step 2. Show glance image using v1 glance api and using curl:
glance --debug --os-image-api-version 1 image-show <uuid>
response: http://paste.openstack.org/show/338515/
curl -v -i -X HEAD -H 'X-Auth-Token: <keystone-token>' http://192.168.0.2:9292/v1/images/<uuid>
response: http://paste.openstack.org/show/338528/
Step 3. Add metadata like in bug: https://bugs.launchpad.net/horizon/+bug/1449260 using horizon or python v2 glance client. e.g.:
cat glance_add_meta.py: http://paste.openstack.org/show/338529/)
python glance_add_meta.py
Step 4. Repead step 2.
Expected result: GET 200 responce
Actual result Responses: 502 Bad Gateway:
curl -v -i -X HEAD -H 'X-Auth-Token: <keystone-token>' http://192.168.0.2:9292/v1/images/<uuid>
response: http://paste.openstack.org/show/338531/
glance --debug --os-image-api-version 1 image-show <uuid>
response: http://paste.openstack.org/show/338533/
------------------------------------------------------------------
If we use for CURl request host ip(bypass httpproxy glance endpoint) we have 200 OK.
curl -v -i -X HEAD -H 'X-Auth-Token: <keystone-token>' http://192.168.0.6:9292/v1/images/<uuid>
response: http://paste.openstack.org/show/338535/ |
If we use http proxy ip like a glance endpoint and add metadata for image in bug: https://bugs.launchpad.net/horizon/+bug/1449260
then http response have wrong HTTP type.
reproduced on branch: stable/juno
Steps to reproduce:
Precondition steps:
httpproxy glance endpoint: http://192.168.0.2:9292
host ip with runned glance-api: 192.168.0.6
Step 1. Create glance image, e.g.:
glance image-create --name test --id <uuid> --disk-format qcow2 --container-format bare --file <file>
response: http://paste.openstack.org/show/338516/
Step 2. Show glance image using v1 glance api and using curl:
glance --debug --os-image-api-version 1 image-show <uuid>
response: http://paste.openstack.org/show/338515/
curl -v -i -X HEAD -H 'X-Auth-Token: <keystone-token>' http://192.168.0.2:9292/v1/images/<uuid>
response: http://paste.openstack.org/show/338528/
Step 3. Add metadata like in bug: https://bugs.launchpad.net/horizon/+bug/1449260 using horizon or python v2 glance client. e.g.:
cat glance_add_meta.py: http://paste.openstack.org/show/338529/)
python glance_add_meta.py
Step 4. Repead step 2.
Expected result: GET 200 responce
Actual result Responses: 502 Bad Gateway:
curl -v -i -X HEAD -H 'X-Auth-Token: <keystone-token>' http://192.168.0.2:9292/v1/images/<uuid>
response: http://paste.openstack.org/show/338531/
glance --debug --os-image-api-version 1 image-show <uuid>
response: http://paste.openstack.org/show/338533/
------------------------------------------------------------------
If we use for CURl request host ip(bypass httpproxy glance endpoint) we have 200 OK.
curl -v -i -X HEAD -H 'X-Auth-Token: <keystone-token>' http://192.168.0.6:9292/v1/images/<uuid>
response: http://paste.openstack.org/show/338535/
If we use for CLI request os-image-url like a host ip (bypass httpproxy glance endpoint) we have 200 OK.
http://paste.openstack.org/show/338561/ |
|
