yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #43220
[Bug 1489059] Re: "db type could not be determined" running py34
Reviewed: https://review.openstack.org/252164
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=768c80765717ce3c4ce224a35389b337c43591ef
Submitter: Jenkins
Branch: master
commit 768c80765717ce3c4ce224a35389b337c43591ef
Author: lvdongbing <dongbing.lv@xxxxxxxxxxxxxxx>
Date: Tue Dec 1 22:38:57 2015 -0500
Put py34 first in the env order of tox
To solve the problem of "db type could not be determined" on py34
we have to run first the py34 env to, then, run py27. This patch
puts py34 first in the tox.ini list of envs to avoid this problem
to happen.
Closes-bug: #1489059
Change-Id: Ia11ecf7bd147e35b7c8ad3db0eaad17f893e78ba
** Changed in: tempest
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1489059
Title:
"db type could not be determined" running py34
Status in Aodh:
Fix Released
Status in Barbican:
Fix Released
Status in cloudkitty:
Fix Committed
Status in Glance:
Fix Committed
Status in glance_store:
Fix Committed
Status in heat:
Fix Released
Status in OpenStack Dashboard (Horizon):
In Progress
Status in Ironic:
Fix Released
Status in ironic-lib:
In Progress
Status in OpenStack Identity (keystone):
Fix Committed
Status in keystoneauth:
Fix Released
Status in keystonemiddleware:
Fix Committed
Status in Manila:
Fix Released
Status in networking-midonet:
In Progress
Status in networking-ofagent:
New
Status in neutron:
Fix Released
Status in python-glanceclient:
Fix Released
Status in python-keystoneclient:
Fix Committed
Status in Sahara:
Fix Released
Status in senlin:
Fix Committed
Status in tap-as-a-service:
New
Status in tempest:
Fix Released
Status in zaqar:
In Progress
Bug description:
When running tox for the first time, the py34 execution fails with an
error saying "db type could not be determined".
This issue is know to be caused when the run of py27 preceeds py34 and
can be solved erasing the .testrepository and running "tox -e py34"
first of all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+subscriptions