config options use-https and https-service-endpoints cannot change
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystone (Juju Charms Collection) |
Fix Released
|
High
|
Edward Hope-Morley |
Bug Description
Deploying keystone with one or more units makes it so that deployers cannot toggle secure endpoints (https) on and off.
This is due to the keystone config-changed charm relying on another trigger when there are peer units, which does not fire.
keystone_hooks.py - L147
...
# Update relations since SSL may have been configured. If we have peer
# units we can rely on the sync to do this in cluster relation.
if is_elected_
...
[ Recreate Steps ]
1. Deploy 2 or more units of Keystone and relate to a service.
2. Enable/disable https service endpoints (juju set keystone https-service-
3. Watch the endpoint listing. It does not change to the appropriate protocol (https/http). It remains stuck.
Related branches
- Liam Young (community): Approve
-
Diff: 315 lines (+84/-71)5 files modifiedhooks/keystone_hooks.py (+30/-55)
hooks/keystone_utils.py (+32/-5)
tests/basic_deployment.py (+0/-1)
unit_tests/test_keystone_hooks.py (+7/-4)
unit_tests/test_keystone_utils.py (+15/-6)
- Liam Young (community): Approve
-
Diff: 317 lines (+83/-74)5 files modifiedhooks/keystone_hooks.py (+29/-55)
hooks/keystone_utils.py (+32/-6)
tests/basic_deployment.py (+0/-1)
unit_tests/test_keystone_hooks.py (+7/-6)
unit_tests/test_keystone_utils.py (+15/-6)
Changed in keystone (Juju Charms Collection): | |
status: | New → In Progress |
Changed in keystone (Juju Charms Collection): | |
status: | In Progress → Fix Released |
Note: this was found on the 15.01 release of the openstack charms.