[openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
Sam.Wan at emc.com
Mon Nov 17 02:16:17 UTC 2014
Seems once I unset ' DEVSTACK_PROJECT_FROM_GIT=python-keystoneclient,python-openstackclient', devstack will fail with ' ERROR: openstack The plugin token_endpoint could not be found'.
How should I overcome this issue then?
Thanks and regards
From: Sean Dague [mailto:sean at dague.net]
Sent: Saturday, November 15, 2014 12:28 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
On 11/14/2014 09:09 AM, Jeremy Stanley wrote:
> On 2014-11-14 00:34:14 -0500 (-0500), Wan, Sam wrote:
>> Seems we need to use python-keystoneclient and python-openstackclient
>> from git.openstack.org because those on pip don’t work.
> That's a bug we're (collectively) trying to prevent in the future.
> Services, even under development, should not depend on features only
> available in unreleased versions of libraries.
>> But in latest update of stack.sh, it’s to use pip by default
> And this is intentional, implemented specifically so that we can keep
> it from happening again.
Patrick actually got to the bottom of a bug we had in devstack around this, we merged the fixes this morning.
As Jeremy said, installing from pypi released versions is intentional.
If something wants to use features in a library, the library needs to cut a release.
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev