yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #42131
[Bug 1489059] Re: "db type could not be determined" running py34
** Also affects: aodh
Importance: Undecided
Status: New
** Changed in: aodh
Assignee: (unassigned) => Shuquan Huang (shuquan)
** Also affects: glance-store
Importance: Undecided
Status: New
** Changed in: glance-store
Assignee: (unassigned) => Shuquan Huang (shuquan)
** Also affects: manila
Importance: Undecided
Status: New
** Changed in: manila
Assignee: (unassigned) => Shuquan Huang (shuquan)
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Assignee: (unassigned) => Shuquan Huang (shuquan)
--
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:
New
Status in cloudkitty:
In Progress
Status in glance_store:
New
Status in heat:
Fix Released
Status in Ironic:
Fix Released
Status in ironic-lib:
In Progress
Status in OpenStack Identity (keystone):
New
Status in Manila:
New
Status in neutron:
Fix Committed
Status in Sahara:
Fix Committed
Status in senlin:
Fix Committed
Status in tempest:
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