[openstack-dev] [neutron][infra] - py34 tests, devstack/base trusty and how does the neutron check pipeline choose between them (oh my)...

Ryan Moats rmoats at us.ibm.com
Sun Aug 9 22:40:33 UTC 2015



I've spent the back half of this week chasing setup failures in the voting
py34 job that is part of the neutron check queue. Here are my two examples:
[1] is the signature that I'm trying to avoid, and [2] is a signature that
I'm happier with because it is more of a real failure...

AFAICT, the key difference between these two signatures is the image loaded
for testing. The first used devstack-trusty and the second used
bare-trusty-1438870493.template.openstack.org. Now, I may be wrong,
but it looks to me like devstack-trusty doesn't have the same packages
installed, as it tries to build
various needed extensions from source code and fails on missing the
python3-dev package.  OTOH, the bare-trusty
image is quite happy at this point.

What isn't quite clear to me (yet) from looking at the
openstack-infra/project-config setup is how the different images are
chosen, so I'm not sure yes if the selection of devstack-trusty for [1] is
the bug,
or the fact that devstack-trusty is missing pieces that bare-trusty has is
the bug.

Looking for help from knowledgeable people about how to go about getting
this addressed.

Thanks,
Ryan Moats
IRC: regXboi

[1]
http://logs.openstack.org/05/144205/3/check/gate-neutron-python34/3f6f7bf/console.html.gz
[2]
http://logs.openstack.org/89/160289/6/check/gate-neutron-python34/ed3ccec/console.html.gz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150809/e37f70de/attachment.html>


More information about the OpenStack-dev mailing list