yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: keystone
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1201380

Title:
  SQL migration for sqlite broken at the 015 (tenant->project) step

Status in OpenStack Identity (Keystone):
  Fix Released

Bug description:
  During the 015 tenant->project migration, any FKs that reference the
  (about to be deleted) tenant table are switched to point at the new
  project table.  However, for sqlite, the group_project_metadata table
  was missed and remains pointing at the old tenant table.  Migrations
  for MySQL and Postgresql are not affected and correctly change the
  FKs.

  This means that any future calls to load that table in migrations
  scripts using sqlite fails trying to load the (now deleted) tenant
  table.  This first becomes a real problem in migration script 028
  which attempts to re-structure the roles metadata - and hence this
  does not support migration via sqlite.

  Our options are:

  a) Write a special migration that goes under the cover and tries to fix up the FK for sqlite
  b) We stop supporting migrations with sqlite

  The real issue here is that you are limited by what kind of table
  modifications are supported with sqlite - which often requires a
  separate code path for any such table altering.  It is this separate
  code path that was wrong in 015.

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