[Openstack-operators] folsom -> grizzly keystone-manage db_sync error

Jonathan Proulx jon at jonproulx.com
Tue Aug 6 13:05:52 UTC 2013

I believe this relates to deleted users.

The old metadata table has entries for user_id's that have no corresponding
entry in the user table.  I've not quite worked out the SQL for showing
these lines but it appears they also have no roles in the projects they are
associated with.  Just a little more coffee and I think I've got it.

If my suspicion is correct then the patch is pretty easy just don't try to
migrate rows where the role list is null.


On Tue, Aug 6, 2013 at 8:38 AM, Jonathan Proulx <jon at jonproulx.com> wrote:

> On Tue, Aug 6, 2013 at 2:15 AM, Robert van Leeuwen <
> Robert.vanLeeuwen at spilgames.com> wrote:
>>  > On Ubuntu 12.04 using cloud-archieve repos I just upgraded  keystone
>> to grizzly from folsom,
>> > but 'keystone-manage db_sync' is failing with something like:
>> > sqlalchemy.exc.IntegrityError: (IntegrityError) (1452, 'Cannot add or
>> update a child row: a foreign key
>>  > Any clues on how to get my db to sync?
>>  Jon,
>> Could you check if your tables are innodb?
>> I've seen something similar when the tables where myisam.
>> Cheers,
>> Robert van Leeuwen
> They are innodb, SHOW TABLE STATUS confirms.
> Thanks,
> -Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130806/385a7766/attachment.html>

More information about the OpenStack-operators mailing list