No module named ibm_db_sa: All jenkins jobs fail

Bug #1287404 reported by fumihiko kakuma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
New
Undecided
Unassigned

Bug Description

I get the following message from jenkins test results:

2014-03-03 15:10:03.580 | + mysql -uroot -psecret -h127.0.0.1 -e 'DROP DATABASE IF EXISTS keystone;'
2014-03-03 15:10:03.582 | + mysql -uroot -psecret -h127.0.0.1 -e 'CREATE DATABASE keystone CHARACTER SET utf8;'
2014-03-03 15:10:03.584 | + /opt/stack/new/keystone/bin/keystone-manage db_sync
2014-03-03 15:10:03.585 | Traceback (most recent call last):
2014-03-03 15:10:03.587 | File "/opt/stack/new/keystone/bin/keystone-manage", line 36, in <module>
2014-03-03 15:10:03.589 | from keystone import cli
2014-03-03 15:10:03.591 | File "/opt/stack/new/keystone/keystone/cli.py", line 19, in <module>
2014-03-03 15:10:03.593 | from migrate import exceptions
2014-03-03 15:10:03.595 | File "/usr/local/lib/python2.7/dist-packages/migrate/__init__.py", line 11, in <module>
2014-03-03 15:10:03.597 | from migrate.changeset import *
2014-03-03 15:10:03.598 | File "/usr/local/lib/python2.7/dist-packages/migrate/changeset/__init__.py", line 22, in <module>
2014-03-03 15:10:03.600 | from migrate.changeset.schema import *
2014-03-03 15:10:03.602 | File "/usr/local/lib/python2.7/dist-packages/migrate/changeset/schema.py", line 15, in <module>
2014-03-03 15:10:03.604 | from migrate.changeset.databases.visitor import (get_engine_visitor,
2014-03-03 15:10:03.606 | File "/usr/local/lib/python2.7/dist-packages/migrate/changeset/databases/visitor.py", line 7, in <module>
2014-03-03 15:10:03.608 | from migrate.changeset.databases import (sqlite,
2014-03-03 15:10:03.610 | File "/usr/local/lib/python2.7/dist-packages/migrate/changeset/databases/ibmdb2.py", line 7, in <module>
2014-03-03 15:10:03.611 | from ibm_db_sa import base
2014-03-03 15:10:03.613 | ImportError: No module named ibm_db_sa
2014-03-03 15:10:03.615 | + exit_trap
2014-03-03 15:10:03.617 | + local r=1
2014-03-03 15:10:03.619 | ++ jobs -p
2014-03-03 15:10:03.621 | + jobs=20532
2014-03-03 15:10:03.623 | + [[ -n 20532 ]]
2014-03-03 15:10:03.624 | + echo 'exit_trap: cleaning up child processes'
2014-03-03 15:10:03.626 | exit_trap: cleaning up child processes
2014-03-03 15:10:03.628 | + kill 20532
2014-03-03 15:10:03.630 | + exit 1

It seems to me that gate-test is much unstable.
In spite of the fact that a build succeeded on a previous stage, all jobs failed on a next stage.

Full logs of all jobs addressed the following:

http://logs.openstack.org/03/71803/4/gate/gate-devstack-dsvm-cells/7a31981

http://logs.openstack.org/03/71803/4/gate/gate-tempest-dsvm-full/aafaee9

http://logs.openstack.org/03/71803/4/gate/gate-tempest-dsvm-postgres-full/46087d0

http://logs.openstack.org/03/71803/4/gate/gate-tempest-dsvm-neutron/0914c69

http://logs.openstack.org/03/71803/4/gate/gate-tempest-dsvm-neutron-large-ops/41e8107

http://logs.openstack.org/03/71803/4/gate/gate-grenade-dsvm/7778822

http://logs.openstack.org/03/71803/4/gate/gate-swift-dsvm-functional/1f994fe

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.