Keystone should be restarted when changing backend to ldap

Bug #1536089 reported by Nicolas Thomas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Keystone Charm
Triaged
Medium
Unassigned
keystone (Juju Charms Collection)
Invalid
Medium
Unassigned

Bug Description

How to reproduce :
 changes keystone.conf to use ldap (or sql), and then goes trying to create users
  but ... it doesn't restart keystone service before adding users.

It should switch to newly configured backend prior to do settings.

Tags: ldap
James Page (james-page)
tags: added: ldap
Changed in keystone (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Medium
James Page (james-page)
Changed in charm-keystone:
importance: Undecided → Medium
status: New → Triaged
Changed in keystone (Juju Charms Collection):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.