Comment 1 for bug 1419043

It looks like keystone races in setting up default role when creating 2 users simultaneously.

2015-02-06 15:27:17.980468 25961 INFO keystone.assignment.core [-] Creating the default role 9fe2ff9ee4384b1894a90878d3e92bab because it does not exist.
2015-02-06 15:27:17.982766 25959 INFO keystone.assignment.core [-] Creating the default role 9fe2ff9ee4384b1894a90878d3e92bab because it does not exist.
2015-02-06 15:27:17.988287 25959 DEBUG keystone.common.sql.core [-] Conflict role: (IntegrityError) (1062, "Duplicate entry '9fe2ff9ee4384b1894a90878d3e92bab' for key 'PRIMARY'") 'INSERT INTO role (id, name, extra) VALUES (%s, %s, %s)' ('9fe2ff9ee4384b1894a90878d3e92bab', '_member_', '{}') wrapper /opt/stack/new/keystone/keystone/common/sql/core.py:399
2015-02-06 15:27:17.988978 25959 WARNING keystone.common.wsgi [-] Conflict occurred attempting to store role - Duplicate Entry

That speaks to a deep race in the keystone allocator that should be fixed.