yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

I believe is not a bug for neutron anymore since the fix for oslo.db has
been release long time ago.

** Changed in: neutron
       Status: Triaged => 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/1227321

Title:
  DBDuplicateEntry not being translated for DB2

Status in OpenStack Image Registry and Delivery Service (Glance):
  Triaged
Status in Orchestration API (Heat):
  In Progress
Status in OpenStack Identity (Keystone):
  Fix Released
Status in OpenStack Neutron (virtual network service):
  Fix Released
Status in OpenStack Compute (Nova):
  Fix Released
Status in The Oslo library incubator:
  Fix Released

Bug description:
  The
  tempest.api.compute.keypairs.test_keypairs.test_create_keypair_with_duplicate_name
  test fails if you're running with a DB2 backend because the nova code
  is not currently translating the db integrity error if the backing
  engine is DB2 (ibm_db_sa) in
  nova.openstack.common.db.sqlalchemy.session._raise_if_duplicate_entry_error.

  Per full disclosure, nova is not claiming support for DB2 and there is
  a lot of work that would need to be done for that which my team is
  planning for icehouse and there is a blueprint here:

  https://blueprints.launchpad.net/nova/+spec/db2-database

  My team does have DB2 10.5 working with nova trunk but we have changes
  to the migration scripts to support that.  Also, you have to run with
  the DB2 patch for sqlalchemy-migrate posted here:

  https://code.google.com/p/sqlalchemy-migrate/issues/detail?id=151

  And you must run with the ibm-db/ibm-db-sa drivers:

  https://code.google.com/p/ibm-db/source/clones?repo=ibm-db-sa

  We're trying to get the sqlalchemy-migrate support for DB2 accepted in
  the icehouse timeframe but need to show the migrate maintainer that he
  can use the free express-c version of DB2 in ubuntu for the test
  backend.

  Anyway, having said all that, fixing the DBDuplicateEntry translation
  is part of the story so I'm opening a bug to track it and get the
  patch up to get the ball rolling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1227321/+subscriptions