Red Hat Bugzilla – Bug 905081
glance endpoint url contains version which brakes new-enough python-glanceclient
Last modified: 2016-04-26 18:29:40 EDT
Description of problem: After installation of OpenStack using packstack, the glance/image endpoint URL looks like http://192.168.32.1:9292/v1. But newer versions of glance-client libraries are appending version part on it's own and it results in urls containing "/v1/v1/{path}" which breaks glance-client functionality (fails with 404). This could be a problem when bug #896154 will be fixed. Also this maybe can be a problem if user specifies --os-image-api-version itself. Version-Release number of selected component (if applicable): Name : openstack-packstack Arch : noarch Version : 2012.2.2 Release : 0.5.dev318.el6ost How reproducible: Steps to Reproduce: 1. Install openstack using openstack-packstack. 2. Check output of keystone endpoint-list Actual results: Contains endpoint url(s) with version hardcoded Expected results: Just server ip/address and port in url. Additional info: - From feedback on irc this is somewhat related to puppet files used by packstack: https://github.com/puppetlabs/puppetlabs-glance/blob/master/manifests/keystone/auth.pp#L53 . - It should be maybe noted that the version in url is also specified in https://github.com/openstack/keystone/blob/master/tools/sample_data.sh#L182 . - This is maybe also relevant for other endpoint urls containing hardcoded version like keystone endpoint but I didn't checked it.
This is already fixed upstream, so we only need to update our glance module: https://github.com/puppetlabs/puppetlabs-glance/commit/51dc02d14580747b360bfdba2e3f8f9219134ac3
> - It should be maybe noted that the version in url is also specified in > https://github.com/openstack/keystone/blob/master/tools/sample_data.sh#L182 . This upstream review fixes that https://review.openstack.org/#/c/22237
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0671.html