I am also still seeing issues with 'ERROR: openstack The plugin
token_endpoint could not be found', we can work around it by adding in a
list of all the clients to DEVSTACK_PROJECT_FROM_GIT and things go back to
working, for example:

http://ec2-54-69-107-106.us-west-2.compute.amazonaws.com/purestorageci/71/131871/10/check/dsvm-tempest-volume-PureISCSIDriver/8e36386/devstacklog.txt

But without it, attempting to use the released versions from pip:

http://ec2-54-69-107-106.us-west-2.compute.amazonaws.com/purestorageci/95/114395/11/check/dsvm-tempest-volume-PureISCSIDriver/725f580/devstacklog.txt

The strange part is that on my development setup, which is watching
sandbox, I was able to pip uninstall the python-*client packages and it
went back to running with out any problems,  (
http://ec2-54-69-246-234.us-west-2.compute.amazonaws.com/purestorageci/MANUALLY_TRIGGERED_282/devstacklog.txt
) but my "live" setup did not after going through the same process.

For now things seem ok with getting the packages from git, but it does
concern me that our CI is not able to function the same way as the gate
jenkins. I would rather have our configuration match those as closely as
possible.

I'm happy to provide more details about the setup or the failures. Any
suggestions on how to go about troubleshooting this would be much
appreciated.


-Patrick

On Mon, Nov 17, 2014 at 3:11 AM, Sean Dague <s...@dague.net> wrote:

> There needs to be a lot more context than that provided. As seen here -
> https://review.openstack.org/#/c/134379/ this seems to be working fine
> upstream.
>
>         -Sean
>
> On 11/16/2014 09:16 PM, Wan, Sam wrote:
> > Hi Sean,
> >
> >   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
> > Sam
> >
> > -----Original Message-----
> > From: Sean Dague [mailto:s...@dague.net]
> > Sent: Saturday, November 15, 2014 12:28 AM
> > To: openstack-dev@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.
> >
> >       -Sean
> >
> > --
> > Sean Dague
> > http://dague.net
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> --
> Sean Dague
> http://dague.net
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to