On 03/04/2014 12:28 AM, Lucas Nussbaum wrote: > Package: glance > Version: 2013.2.2-2 > Severity: serious > Justification: renders package unusable > > Hi, > > After installing glance, I get the following errors in the log: > 2014-03-03 16:11:23.179 17528 WARNING glance.store.base [-] Failed to > configure store correctly: Store sheepdog could not be configured correctly. > Reason: Error in store configuration: Unexpected error while running command. > Command: collie > Exit code: 127 > Stdout: '' > Stderr: '/bin/sh: 1: collie: not found\n' Disabling add method. > 2014-03-03 16:11:23.202 17528 WARNING glance.store.base [-] Failed to > configure store correctly: Store cinder could not be configured correctly. > Reason: Cinder storage requires a context. Disabling add method. > 2014-03-03 16:11:23.448 17528 WARNING keystoneclient.middleware.auth_token > [-] Configuring auth_uri to point to the public identity endpoint is > required; clients may not be able to authenticate against an admin endpoint > > Installing sheepdog fixes the first warning. > > installing python-cinderclient apparently fixes the second warning. > > Configuring auth_uri in glance-api.conf fixes the third one: > [keystone_authtoken] > auth_host = 127.0.0.1 > auth_port = 35357 > auth_protocol = http > auth_uri = http://127.0.0.1:35357 > > > Lucas
Hi Lucas, If I understand well, you've been able to fix everything. How come then it's a "serious" issue that makes "package unusable"? Also, this seems related to using sheepdog, which I never used. I'm convince that the default setup of Glance (using keystone and the local file-based store) works out of the box, and we've been using RDB (using Ceph) without issue. It looks like to me that the only thing we should fix is add python-cinderclient as dependency, and completely removing the auth_uri parameter of the default config file (so that other directives are in use by default). Your thoughts? I'll be waiting for more input from you, Cheers, Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
