On 08:49 Jun 23, Mike Perez wrote: > There was a bug raised [1] from some large deployments that the Cinder > client 1.2.0 and beyond is not working because of version discovery. > Unfortunately it's not taking into account of deployments that have a > proxy. > > Cinder client asks Keystone to find a publicURL based on a version. > Keystone will gather data from the service catalog and ask Cinder for > a list of the public endpoints and compare. For the proxy cases, > Cinder is giving internal URLs back to the proxy and Keystone ends up > using that instead of the publicURL in the service catalog. As a > result, clients usually won't be able to use the internal URL and > rightfully so. > > This is all correctly setup on the deployer's side, this an issue with > the server side code of Cinder. > > There is a patch that allows the deployer to specify a configuration > option public_endpoint [2] which was introduced in a patch in Kilo > [3]. The problem though is we can't expect people to already be > running Kilo to take advantage of this, and it leaves deployers > running stable releases of Juno in the dark with clients upgrading and > using the latest. > > Two options: > > 1) Revert version discovery which was introduced in Kilo for Cinder client. > > 2) Grant exception on backporting [4] a patch that helps with this > problem, and introduces a config option that does not change default > behavior. I'm also not sure if this should be considered for Icehouse.
As decided, we went with option 1 and reverted version discovery in 1.3.1 of python-cinderclient for now. -- Mike Perez __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev