[openstack-dev] [infra][python3][congress] locally successful devstack setup fails in check-job
cboylan at sapwetik.org
Wed Jul 19 20:11:31 UTC 2017
On Tue, Jul 18, 2017, at 12:47 PM, Eric K wrote:
> Hi all, looking for some hints/tips. Thanks so much in advance.
> My local python3 devstack setup  succeeds, but in check-job a
> configured devstack setup  fails for not installing congress client.
> [ERROR] /opt/stack/new/devstack/inc/python:401 The following
> were not installed correct: python-congressclient
> It seems that the devstack setup in check-job never attempted to install
> congress client. Comparing the log  in my local run to the log in
> check-job , all these steps in my local log are absent from the
> check-job log:
> Cloning into '/opt/stack/python-congressclient'
You won't see this logged by devstack because devstack-gate does all of
the git repo setup beforehand to ensure that the correct git refs are
> Check python version for : /opt/stack/python-congressclient
> Automatically using 3.5 version to install
> /opt/stack/python-congressclient based on classifiers
> Installing collected packages: python-congressclient
> Running setup.py develop for python-congressclient
> Successfully installed python-congressclient
>  Check-job config:
>  Local devstack local.conf:
>  Check-job devstack log:
>  Local devstack log:
My best guess of what is happening here is that python-congressclient is
being installed to python2 from source so then when devstack checks if
python-congressclient is installed properly against python3 it fails.
You'll want to make sure that whatever is installing
python-congressclient is doing so against the appropriate python.
More information about the OpenStack-dev