keystone-manage bootstrap does not work for non-SQL identity drivers
Bug #1553216 reported by
Matthew Edmonds
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Kristi Nikolla |
Bug Description
keystone-manage bootstrap attempts to create the specified user and then handles a Conflict error as notice that the user already exists. This works for the default SQL identity driver, but does not work for drivers that do not support creating users. In order to work for all drivers, which is necessary to support role assignment bootstrapping whenever the driver configuration is changed, it should attempt to GET the user or otherwise check in a way that will work for drivers that do not support user creation.
tags: | added: rc-potential |
Changed in keystone: | |
milestone: | none → mitaka-rc1 |
Changed in keystone: | |
assignee: | nobody → Kristi Nikolla (knikolla) |
Changed in keystone: | |
assignee: | Kristi Nikolla (knikolla) → Steve Martinelli (stevemar) |
Changed in keystone: | |
assignee: | Steve Martinelli (stevemar) → Kristi Nikolla (knikolla) |
tags: | removed: rc-potential |
To post a comment you must log in.
To generalize this further, it sounds like the bootstrap command should become an idempotent operation?