Description of problem: assignment table migration fails for keystone-manage db_sync if duplicate entry exists When moving from Havana to Icehouse (Keystone version 38 -> 44) and keystone-manage db_sync runs, it fails if there are duplicate project entries. 2014-11-24 23:12:58.701 9239 CRITICAL keystone [-] IntegrityError: (IntegrityError) (1062, "Duplicate entry 'UserProject-096cb95691404a959289200afa7d4b2f-c0036d48a8524cf6ba1' for key 'PRIMARY'") 'INSERT INTO assignment (type, actor_id, target_id, role_id, inherited) VALUES (%s, %s, %s, %s, %s)' ('UserProject', '096cb95691404a959289200afa7d4b2f', 'c0036d48a8524cf6ba1ed6e857649989', '9fe2ff9ee4384b1894a90878d3e92bab', False)
> it fails if there are duplicate project entries What could cause duplicates, was unique constraint missing in Havana and is it there now?
I never got a final answer as to the cause of the problem. Need to know if it is still a real issue, as it should not be. The upstream changes have been collapsed, so it would be a backport only patch if required. The original author has not resubmitted since the merge conflict.
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.