yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #05017
[Bug 1227321] Re: DBDuplicateEntry not being translated for DB2
Because we don't currently support DB2, I gave this bug minimum priority
just to get it out of the new-bugs-to-triage queue. If nobody were
working on it I'd mark it closed/wontfix, but since someone is working
on it, it's fine to leave it in the tracker for later.
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1227321
Title:
DBDuplicateEntry not being translated for DB2
Status in OpenStack Compute (Nova):
Opinion
Status in Oslo - a Library of Common OpenStack Code:
In Progress
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/nova/+bug/1227321/+subscriptions