yahoo-eng-team team mailing list archive

[OpenStack Infra <1489059@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/262044
Committed: https://git.openstack.org/cgit/openstack-dev/hacking/commit/?id=a73d9c20314594cefede02841536ecca9a89906b
Submitter: Jenkins
Branch:    master

commit a73d9c20314594cefede02841536ecca9a89906b
Author: janonymous <janonymous.codevulture@xxxxxxxxx>
Date:   Mon Dec 28 22:43:37 2015 +0530

    Put py34 first in the env order of tox
    
    To solve the problem of "db type could not be determined" we have to run
    first the py34 env and then py2x. This patch puts py34 first on the
    tox.ini list of envs to avoid this problem.
    
    Change-Id: Ie22758ae555412689964e1a681a8bdb365b4b5e7
    Closes-bug: #1489059


** Changed in: hacking
       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 hacking:
  Fix Released
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Committed
Status in Manila:
  Fix Released
Status in Murano:
  Fix Committed
Status in networking-midonet:
  Fix Released
Status in networking-ofagent:
  New
Status in neutron:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-keystoneclient:
  Fix Committed
Status in python-muranoclient:
  Fix Released
Status in python-solumclient:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Released
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