LDAP config conversion from Juno to Kilo

Bug #1506597 reported by Bjoern
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Medium
Unassigned
Kilo
Fix Released
Medium
Jimmy McCrory
Trunk
Invalid
Medium
Unassigned

Bug Description

As part of the upgrade procedure we are currently converting the LDAP setting from a key/value representation to a YAML like:

keystone_ldap_server converts to

keystone_ldap:
  ldap:
  server:xxx

but this is unfortunately not enough because we need to rename the attributes too like :

keystone_ldap_server -> url
keystone_ldap_user_bind -> user
keystone_ldap_user_bind_password -> password

so we would end up with :

keystone_ldap:
  ldap:
    url: http://server
    user: xxx
    password: xxx

Otherwise we would generate a invalid keystone ldap configuration with the missing user, password and url values.
I'm currently only aware of those 3 keys which need to be renamed throughout the process.

Changed in openstack-ansible:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/241809

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (kilo)

Reviewed: https://review.openstack.org/241809
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=afa1c8fb281f4a2f2e5c4118dbdce6d1a3daab4f
Submitter: Jenkins
Branch: kilo

commit afa1c8fb281f4a2f2e5c4118dbdce6d1a3daab4f
Author: Jimmy McCrory <email address hidden>
Date: Wed Nov 4 15:04:34 2015 -0800

    Rename Keystone LDAP entries during Kilo upgrade

    In Juno, a few Keystone LDAP variables had names differing from the
    associated configuration options.
    Through the juno-kilo-ldap-conversion.py script, ensure that these
    variables are renamed when upgrading to Kilo.

    Change-Id: I49b5352173b01cad65d7581a22923adedb0beec2
    Closes-Bug: #1506597

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.15

This issue was fixed in the openstack/openstack-ansible 11.2.15 release.

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.