Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
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
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
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
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
Hi Gord,
Seems this not work for me. I've pip uninstalled all python-*client .
# pip list|grep -P 'python-.*client'
python-barbicanclient (3.0.1)
python-ceilometerclient (1.0.12)
python-cinderclient (1.1.1)
python-glanceclient (0.14.2)
python-heatclient (0.2.12)
python-keystoneclient (0.11.2)
python-neutronclient (2.3.9)
python-novaclient (2.20.0)
python-openstackclient (0.4.1)
python-saharaclient (0.7.5)
python-swiftclient (2.3.1)
python-troveclient (1.0.7)
# pip list|grep -P 'python-.*client'|awk '{print $1}'|while read pn; do pip
uninstall -y $pn; done
Uninstalling python-barbicanclient:
Successfully uninstalled python-barbicanclient
Uninstalling python-ceilometerclient:
Successfully uninstalled python-ceilometerclient
Uninstalling python-cinderclient:
Successfully uninstalled python-cinderclient
Uninstalling python-glanceclient:
Successfully uninstalled python-glanceclient
Uninstalling python-heatclient:
Successfully uninstalled python-heatclient
Uninstalling python-keystoneclient:
Successfully uninstalled python-keystoneclient
Uninstalling python-neutronclient:
Successfully uninstalled python-neutronclient
Uninstalling python-novaclient:
Successfully uninstalled python-novaclient
Uninstalling python-openstackclient:
Successfully uninstalled python-openstackclient
Uninstalling python-saharaclient:
Successfully uninstalled python-saharaclient
Uninstalling python-swiftclient:
Successfully uninstalled python-swiftclient
Uninstalling python-troveclient:
Successfully uninstalled python-troveclient
root@vnxslave2:~# pip list|grep -P 'python-.*client'
root@vnxslave2:~#
But devstack still failed with same errors.
Thanks and regards
Sam
From: gordon chung [mailto:g...@live.ca]
Sent: Saturday, November 15, 2014 12:12 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [infra][devstack] CI failed The plugin
token_endpoint could not be found
just an fyi, i had same issue. i 'pip uninstall'ed all the python-*clients and
it worked fine... i assume it's something to do with master (as i had it
configured previously) since devstack seems to pull in pypi version.
cheers,
gord
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
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
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
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. -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
just an fyi, i had same issue. i 'pip uninstall'ed all the python-*clients and it worked fine... i assume it's something to do with master (as i had it configured previously) since devstack seems to pull in pypi version. cheers, gord ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
I'm running into this issue as well on my CI. Any ideas on how to fix this? My CI is behaving similar to the official jenkins in regards to using pip to install the clients, and pip freeze shows the same versions on each. Comparing http://logs.openstack.org/70/124370/7/check/check-tempest-dsvm-full/d6a53b7/logs/devstacklog.txt.gz#_2014-11-13_18_48_32_860 and the same spot in http://ec2-54-69-246-234.us-west-2.compute.amazonaws.com/purestorageci/MANUALLY_TRIGGERED_272/devstacklog.txt they both fail use_library_from_git check for keystoneclient and openstackclient Any suggestions would be much appreciated! -Patrick On Wed, Nov 12, 2014 at 10:22 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, I'm wondering why you are just hitting it now? Does your CI pull the latest python-keystoneclient and python-openstackclient from master? Yes before it began to fail, but now it is No because of this change: https://github.com/openstack-dev/devstack/commit/8f8e2d1fbfa4c51f6b68a6967e330cd478f979ee Now python-*client are installed by pip install instead of git clone. I think this change causes the problem. But I don't understand why there are success CIs and failed CIs (include mine) and how to fix the problem. Thanks. Itsuro Oda On Thu, 13 Nov 2014 00:36:41 -0500 Steve Martinelli steve...@ca.ibm.com wrote: About a month ago, we made changes to python-openstackclient that seem related to the error message you posted. Change is https://review.openstack.org/#/c/127655/3/setup.cfg I'm wondering why you are just hitting it now? Does your CI pull the latest python-keystoneclient and python-openstackclient from master? Thanks, _ Steve Martinelli OpenStack Development - Keystone Core Member Phone: (905) 413-2851 E-Mail: steve...@ca.ibm.com From: Itsuro ODA o...@valinux.co.jp To: openstack-dev@lists.openstack.org Date: 11/12/2014 11:27 PM Subject:[openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found Hi, My third party CI becomes failed from about 21:00 12th UTC in execution of devstack. The error occurs at openstack project create admin -f value -c id --- ERROR: openstack The plugin token_endpoint could not be found --- I found some CIs have same problem. Does anyone give me a hint to solve this problem ? Thanks. -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- -Patrick ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
Hi,
Seems we need to use python-keystoneclient and python-openstackclient from
git.openstack.org because those on pip don’t work.
But in latest update of stack.sh, it’s to use pip by default
if use_library_from_git python-openstackclient; then
git_clone_by_name python-openstackclient
setup_dev_lib python-openstackclient
else
pip_install python-openstackclient
fi
By looking at use_library_from_git in functions-common, you’ll see
function use_library_from_git {
local name=$1
local enabled=1
[[ ,${LIBS_FROM_GIT}, =~ ,${name}, ]] enabled=0
return $enabled
}
LIBS_FROM_GIT which gets it value from DEVSTACK_PROJECT_FROM_GIT
(devstack-gate/devstack-vm-gate.sh), by default, is empty.
I think we should set default value for DEVSTACK_PROJECT_FROM_GIT to fix this.
And by now, we can work around this issue by setting DEVSTACK_PROJECT_FROM_GIT
in our CI.
export DEVSTACK_PROJECT_FROM_GIT=python-keystoneclient,python-openstackclient
This works for me. Hope it helps.
Thanks and regards
Sam
From: Patrick East [mailto:patrick.e...@purestorage.com]
Sent: Friday, November 14, 2014 4:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [infra][devstack] CI failed The plugin
token_endpoint could not be found
I'm running into this issue as well on my CI. Any ideas on how to fix this?
My CI is behaving similar to the official jenkins in regards to using pip to
install the clients, and pip freeze shows the same versions on each.
Comparing
http://logs.openstack.org/70/124370/7/check/check-tempest-dsvm-full/d6a53b7/logs/devstacklog.txt.gz#_2014-11-13_18_48_32_860
and the same spot in
http://ec2-54-69-246-234.us-west-2.compute.amazonaws.com/purestorageci/MANUALLY_TRIGGERED_272/devstacklog.txt
they both fail use_library_from_git check for keystoneclient and
openstackclient
Any suggestions would be much appreciated!
-Patrick
On Wed, Nov 12, 2014 at 10:22 PM, Itsuro ODA
o...@valinux.co.jpmailto:o...@valinux.co.jp wrote:
Hi,
I'm wondering why you are just hitting it now? Does your CI pull the
latest python-keystoneclient and python-openstackclient from master?
Yes before it began to fail, but now it is No because of this change:
https://github.com/openstack-dev/devstack/commit/8f8e2d1fbfa4c51f6b68a6967e330cd478f979ee
Now python-*client are installed by pip install instead of git clone.
I think this change causes the problem. But I don't understand
why there are success CIs and failed CIs (include mine) and how to fix
the problem.
Thanks.
Itsuro Oda
On Thu, 13 Nov 2014 00:36:41 -0500
Steve Martinelli steve...@ca.ibm.commailto:steve...@ca.ibm.com wrote:
About a month ago, we made changes to python-openstackclient that seem
related to the error message you posted. Change is
https://review.openstack.org/#/c/127655/3/setup.cfg
I'm wondering why you are just hitting it now? Does your CI pull the
latest python-keystoneclient and python-openstackclient from master?
Thanks,
_
Steve Martinelli
OpenStack Development - Keystone Core Member
Phone: (905) 413-2851tel:%28905%29%20413-2851
E-Mail: steve...@ca.ibm.commailto:steve...@ca.ibm.com
From: Itsuro ODA o...@valinux.co.jpmailto:o...@valinux.co.jp
To:
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: 11/12/2014 11:27 PM
Subject:[openstack-dev] [infra][devstack] CI failed The plugin
token_endpoint could not be found
Hi,
My third party CI becomes failed from about 21:00 12th UTC
in execution of devstack.
The error occurs at openstack project create admin -f value -c id
---
ERROR: openstack The plugin token_endpoint could not be found
---
I found some CIs have same problem.
Does anyone give me a hint to solve this problem ?
Thanks.
--
Itsuro ODA o...@valinux.co.jpmailto:o...@valinux.co.jp
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Itsuro ODA o...@valinux.co.jpmailto:o...@valinux.co.jp
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
-Patrick
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
Hi, My third party CI becomes failed from about 21:00 12th UTC in execution of devstack. The error occurs at openstack project create admin -f value -c id --- ERROR: openstack The plugin token_endpoint could not be found --- I found some CIs have same problem. Does anyone give me a hint to solve this problem ? Thanks. -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
Hi, My third party CI becomes failed from about 21:00 12th UTC in execution of devstack. The error occurs at openstack project create admin -f value -c id --- ERROR: openstack The plugin token_endpoint could not be found --- does your CI clean $DEST for each runs? i guess you are somehow mixing different versions of code. YAMAMOTO Takashi I found some CIs have same problem. Does anyone give me a hint to solve this problem ? Thanks. -- Itsuro ODA o...@valinux.co.jp ___ 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
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
About a month ago, we made changes to python-openstackclient that seem related to the error message you posted. Change is https://review.openstack.org/#/c/127655/3/setup.cfg I'm wondering why you are just hitting it now? Does your CI pull the latest python-keystoneclient and python-openstackclient from master? Thanks, _ Steve Martinelli OpenStack Development - Keystone Core Member Phone: (905) 413-2851 E-Mail: steve...@ca.ibm.com From: Itsuro ODA o...@valinux.co.jp To: openstack-dev@lists.openstack.org Date: 11/12/2014 11:27 PM Subject:[openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found Hi, My third party CI becomes failed from about 21:00 12th UTC in execution of devstack. The error occurs at openstack project create admin -f value -c id --- ERROR: openstack The plugin token_endpoint could not be found --- I found some CIs have same problem. Does anyone give me a hint to solve this problem ? Thanks. -- Itsuro ODA o...@valinux.co.jp ___ 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
Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found
Hi, I'm wondering why you are just hitting it now? Does your CI pull the latest python-keystoneclient and python-openstackclient from master? Yes before it began to fail, but now it is No because of this change: https://github.com/openstack-dev/devstack/commit/8f8e2d1fbfa4c51f6b68a6967e330cd478f979ee Now python-*client are installed by pip install instead of git clone. I think this change causes the problem. But I don't understand why there are success CIs and failed CIs (include mine) and how to fix the problem. Thanks. Itsuro Oda On Thu, 13 Nov 2014 00:36:41 -0500 Steve Martinelli steve...@ca.ibm.com wrote: About a month ago, we made changes to python-openstackclient that seem related to the error message you posted. Change is https://review.openstack.org/#/c/127655/3/setup.cfg I'm wondering why you are just hitting it now? Does your CI pull the latest python-keystoneclient and python-openstackclient from master? Thanks, _ Steve Martinelli OpenStack Development - Keystone Core Member Phone: (905) 413-2851 E-Mail: steve...@ca.ibm.com From: Itsuro ODA o...@valinux.co.jp To: openstack-dev@lists.openstack.org Date: 11/12/2014 11:27 PM Subject:[openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found Hi, My third party CI becomes failed from about 21:00 12th UTC in execution of devstack. The error occurs at openstack project create admin -f value -c id --- ERROR: openstack The plugin token_endpoint could not be found --- I found some CIs have same problem. Does anyone give me a hint to solve this problem ? Thanks. -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
