Re: [openstack-dev] [infra][python3][congress] locally successful devstack setup fails in check-job

2017-07-19 Thread Eric K


On 7/19/17, 1:11 PM, "Clark Boylan"  wrote:

>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 [2] succeeds, but in check-job a
>> similarly
>> configured devstack setup [1] fails for not installing congress client.
>> 
>> ./stack.sh:1439:check_libs_from_git
>> /opt/stack/new/devstack/inc/python:401:die
>> [ERROR] /opt/stack/new/devstack/inc/python:401 The following
>> LIBS_FROM_GIT
>> were not installed correct: python-congressclient
>> 
>> 
>> It seems that the devstack setup in check-job never attempted to install
>> congress client. Comparing the log [4] in my local run to the log in
>> check-job [3], all these steps in my local log are absent from the
>> check-job log:
>> ++/opt/stack/congress/devstack/settings:source:9
>> CONGRESSCLIENT_DIR=/opt/stack/python-congressclient
>> 
>> ++/opt/stack/congress/devstack/settings:source:52
>> 
>>CONGRESSCLIENT_REPO=git://git.openstack.org/openstack/python-congressclie
>>nt
>> .git
>> 
>> 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
>checked out.
>
>> 
>> 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
>> 
>> 
>> [1] Check-job config:
>> 
>>https://github.com/openstack-infra/project-config/blob/master/jenkins/job
>>s/
>> congress.yaml#L65
>> 
>>https://github.com/openstack-infra/project-config/blob/master/jenkins/job
>>s/
>> congress.yaml#L111
>> 
>> [2] Local devstack local.conf:
>> https://pastebin.com/qzuYTyAE
>> 
>> [3] Check-job devstack log:
>> 
>>http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-m
>>ys
>> ql-ubuntu-xenial-nv/7ae2814/logs/devstacklog.txt.gz
>> 
>> [4] Local devstack log:
>> https://ufile.io/c9jhm
>
>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.

Thanks a lot Clark!

Now pursuing the guess that install was done in wrong python version.

I was actually looking at the wrong log. Here is the correct one.
http://logs.openstack.org/53/485053/1/check/gate-congress-dsvm-py35-api-mys
ql-ubuntu-xenial-nv/7f07b73/logs/devstacklog.txt.gz

In this log, I see it successfully installing congress client here:
| Installing collected packages: python-congressclient

| Running setup.py develop for python-congressclient

| Successfully installed python-congressclient

| + ./stack.sh:main:941 : use_library_from_git python-openstackclient

| + inc/python:use_library_from_git:378 : local enabled=1
| + inc/python:use_library_from_git:379 : [[ python-congressclient =
\A\L\L ]]
| + inc/python:use_library_from_git:379 : [[ ,python-congressclient, =~
,python-openstackclient, ]]
| + inc/python:use_library_from_git:380 : return 1

(http://logs.openstack.org/53/485053/1/check/gate-congress-dsvm-py35-api-my
sql-ubuntu-xenial-nv/7f07b73/logs/devstacklog.txt.gz#_2017-07-19_06_26_31_5
46)

From then on there is nothing noteworthy re: congress client until it says
the client is not installed correctly:
| + inc/python:check_libs_from_git:395 : lib_installed_from_git
python-congressclient

...
| + inc/python:check_libs_from_git:401 : die 401 'The following
LIBS_FROM_GIT were not installed correct: python-congressclient’

(http://logs.openstack.org/53/485053/1/check/gate-congress-dsvm-py35-api-my
sql-ubuntu-xenial-nv/7f07b73/logs/devstacklog.txt.gz#_2017-07-19_06_36_41_2
01)

Is there a way to tell from these logs whether the install is being done
in python2 or python3? From this line in the log it seems to be doing the
right thing:
| Automatically using 3.5 version to install
/opt/stack/new/python-congressclient based on classifiers

(http://logs.openstack.org/53/485053/1/check/gate-congress-dsvm-py35-api-my
sql-ubuntu-xenial-nv/7f07b73/logs/devstacklog.txt.gz#_2017-07-19_06_26_24_8
86)

Thanks again!



>
>Clark
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [infra][python3][congress] locally successful devstack setup fails in check-job

2017-07-19 Thread Eric K
Thanks a lot Jeremy. I'm now running the reproduce.sh to see what happens.

> [3] Check-job devstack log:
> 
>http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-my
>sql-ubuntu-xenial-nv/7ae2814/logs/devstacklog.txt.gz

And oops, I linked to and older run of the check-job devstack log. Here¹s
a more appropriate version:
http://logs.openstack.org/53/485053/1/check/gate-congress-dsvm-py35-api-mys
ql-ubuntu-xenial-nv/7f07b73/logs/devstacklog.txt.gz

In this log, I see it successfully installing congress client here:
| Installing collected packages: python-congressclient

|   Running setup.py develop for python-congressclient

| Successfully installed python-congressclient

| + ./stack.sh:main:941  :   use_library_from_git
python-openstackclient

| + inc/python:use_library_from_git:378  :   local enabled=1
| + inc/python:use_library_from_git:379  :   [[ python-congressclient
= \A\L\L ]]
| + inc/python:use_library_from_git:379  :   [[
,python-congressclient, =~ ,python-openstackclient, ]]
| + inc/python:use_library_from_git:380  :   return 1

(http://logs.openstack.org/53/485053/1/check/gate-congress-dsvm-py35-api-my
sql-ubuntu-xenial-nv/7f07b73/logs/devstacklog.txt.gz#_2017-07-19_06_26_31_5
46)

From then on there is nothing noteworthy re: congress client until it says
the client is not installed correctly:
| + inc/python:check_libs_from_git:395   :   lib_installed_from_git
python-congressclient

...
| + inc/python:check_libs_from_git:401   :   die 401 'The following
LIBS_FROM_GIT were not installed correct:  python-congressclient¹

(http://logs.openstack.org/53/485053/1/check/gate-congress-dsvm-py35-api-my
sql-ubuntu-xenial-nv/7f07b73/logs/devstacklog.txt.gz#_2017-07-19_06_36_41_2
01)

Clark suggested that perhaps in install for python-congressclient was
going to python2 instead of python3. So I¹m investigating that.

Thanks again!

On 7/19/17, 11:19 AM, "Jeremy Stanley"  wrote:

>On 2017-07-18 12:47:07 -0700 (-0700), Eric K wrote:
>> Hi all, looking for some hints/tips. Thanks so much in advance.
>> 
>> My local python3 devstack setup [2] succeeds, but in check-job a
>>similarly
>> configured devstack setup [1] fails for not installing congress client.
>> 
>> ./stack.sh:1439:check_libs_from_git
>> /opt/stack/new/devstack/inc/python:401:die
>> [ERROR] /opt/stack/new/devstack/inc/python:401 The following
>>LIBS_FROM_GIT
>> were not installed correct: python-congressclient
>> 
>> 
>> It seems that the devstack setup in check-job never attempted to install
>> congress client. Comparing the log [4] in my local run to the log in
>> check-job [3], all these steps in my local log are absent from the
>> check-job log:
>> ++/opt/stack/congress/devstack/settings:source:9
>> CONGRESSCLIENT_DIR=/opt/stack/python-congressclient
>> 
>> ++/opt/stack/congress/devstack/settings:source:52
>> 
>>CONGRESSCLIENT_REPO=git://git.openstack.org/openstack/python-congressclie
>>nt.git
>> 
>> Cloning into '/opt/stack/python-congressclient'
>> 
>> 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
>> 
>> 
>> [1] Check-job config:
>> 
>>https://github.com/openstack-infra/project-config/blob/master/jenkins/job
>>s/congress.yaml#L65
>> 
>>https://github.com/openstack-infra/project-config/blob/master/jenkins/job
>>s/congress.yaml#L111
>> 
>> [2] Local devstack local.conf:
>> https://pastebin.com/qzuYTyAE
>> 
>> [3] Check-job devstack log:
>> 
>>http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-m
>>ysql-ubuntu-xenial-nv/7ae2814/logs/devstacklog.txt.gz
>> 
>> [4] Local devstack log:
>> https://ufile.io/c9jhm
>
>Did you attempt comparison to the local.conf the job used?
>
>http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-my
>sql-ubuntu-xenial-nv/7ae2814/logs/local.conf.txt.gz
>
>Also, if you haven't seen it, every devstack-gate run includes a
>convenience script you should be able to use to reproduce locally
>with the same settings:
>
>http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-my
>sql-ubuntu-xenial-nv/7ae2814/logs/reproduce.sh
>
>Further, https://review.openstack.org/484158 seems to have changed
>the behavior of the job since the log you posted from the 14th. Is
>the result still the same in this case?
>-- 
>Jeremy Stanley
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not 

Re: [openstack-dev] [infra][python3][congress] locally successful devstack setup fails in check-job

2017-07-19 Thread Clark Boylan
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 [2] succeeds, but in check-job a
> similarly
> configured devstack setup [1] fails for not installing congress client.
> 
> ./stack.sh:1439:check_libs_from_git
> /opt/stack/new/devstack/inc/python:401:die
> [ERROR] /opt/stack/new/devstack/inc/python:401 The following
> LIBS_FROM_GIT
> were not installed correct: python-congressclient
> 
> 
> It seems that the devstack setup in check-job never attempted to install
> congress client. Comparing the log [4] in my local run to the log in
> check-job [3], all these steps in my local log are absent from the
> check-job log:
> ++/opt/stack/congress/devstack/settings:source:9
> CONGRESSCLIENT_DIR=/opt/stack/python-congressclient
> 
> ++/opt/stack/congress/devstack/settings:source:52
> CONGRESSCLIENT_REPO=git://git.openstack.org/openstack/python-congressclient
> .git
> 
> 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
checked out.

> 
> 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
> 
> 
> [1] Check-job config:
> https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/
> congress.yaml#L65
> https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/
> congress.yaml#L111
> 
> [2] Local devstack local.conf:
> https://pastebin.com/qzuYTyAE   
> 
> [3] Check-job devstack log:
> http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-mys
> ql-ubuntu-xenial-nv/7ae2814/logs/devstacklog.txt.gz
> 
> [4] Local devstack log:
> https://ufile.io/c9jhm

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.

Clark

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra][python3][congress] locally successful devstack setup fails in check-job

2017-07-19 Thread Jeremy Stanley
On 2017-07-18 12:47:07 -0700 (-0700), Eric K wrote:
> Hi all, looking for some hints/tips. Thanks so much in advance.
> 
> My local python3 devstack setup [2] succeeds, but in check-job a similarly
> configured devstack setup [1] fails for not installing congress client.
> 
> ./stack.sh:1439:check_libs_from_git
> /opt/stack/new/devstack/inc/python:401:die
> [ERROR] /opt/stack/new/devstack/inc/python:401 The following LIBS_FROM_GIT
> were not installed correct: python-congressclient
> 
> 
> It seems that the devstack setup in check-job never attempted to install
> congress client. Comparing the log [4] in my local run to the log in
> check-job [3], all these steps in my local log are absent from the
> check-job log:
> ++/opt/stack/congress/devstack/settings:source:9
> CONGRESSCLIENT_DIR=/opt/stack/python-congressclient
> 
> ++/opt/stack/congress/devstack/settings:source:52
> CONGRESSCLIENT_REPO=git://git.openstack.org/openstack/python-congressclient.git
> 
> Cloning into '/opt/stack/python-congressclient'
> 
> 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
> 
> 
> [1] Check-job config:
> https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/congress.yaml#L65
> https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/congress.yaml#L111
> 
> [2] Local devstack local.conf:
> https://pastebin.com/qzuYTyAE
> 
> [3] Check-job devstack log:
> http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-mysql-ubuntu-xenial-nv/7ae2814/logs/devstacklog.txt.gz
> 
> [4] Local devstack log:
> https://ufile.io/c9jhm

Did you attempt comparison to the local.conf the job used?

http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-mysql-ubuntu-xenial-nv/7ae2814/logs/local.conf.txt.gz

Also, if you haven't seen it, every devstack-gate run includes a
convenience script you should be able to use to reproduce locally
with the same settings:

http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-mysql-ubuntu-xenial-nv/7ae2814/logs/reproduce.sh

Further, https://review.openstack.org/484158 seems to have changed
the behavior of the job since the log you posted from the 14th. Is
the result still the same in this case?
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev