enabling use-https or https-service-endpoints once either has already been enabled gets ignored

Bug #1415579 reported by Edward Hope-Morley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
keystone (Juju Charms Collection)
Fix Released
High
Edward Hope-Morley

Bug Description

The config-changed hook defers ssl-related config to the cluster relation-changed-hook if num units > 1. Currently the trigger used remains the same once set so if you first enable one of use-https or https-service-endpoints then at some later stage enable the other, the cluster relation hook will not fire.

Note that this is not a problem if enabling both at once and use-https is a subset of https-=service-endpoints anway so the only real transition that produces a problem is:

use-https=no + https-service-endpoints=false => use-https=yes + https-service-endpoints=false => use-https=yes + https-service-endpoints=true

I will look to getting this fixed and backported as soon as 15.01 is cut.

Related branches

summary: enabling use-https or https-service-endpoints once either has already
- been enabled get ignored
+ been enabled gets ignored
tags: added: cts openstack
Changed in keystone (Juju Charms Collection):
milestone: none → 15.04
tags: added: backport-potential
Changed in keystone (Juju Charms Collection):
status: Confirmed → In Progress
assignee: nobody → Edward Hope-Morley (hopem)
importance: Medium → High
Changed in keystone (Juju Charms Collection):
status: In Progress → Fix Committed
Changed in keystone (Juju Charms Collection):
status: Fix Committed → Fix Released
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.