Unpredictable usernames when using defining multiple endpoints
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Keystone Charm |
Fix Released
|
Medium
|
Liam Young | ||
OpenStack Neutron Gateway Charm |
Fix Released
|
Undecided
|
Dmitrii Shcherbakov | ||
OpenStack Nova Cloud Controller Charm |
Fix Released
|
Medium
|
Liam Young |
Bug Description
The trusty icehouse nova-cloud-
DEBUG:runner:
DEBUG:runner:
Looking at that output: s3_ec2_nova != s3_nova_ec2
I can't figure out what triggered this to start happening or why it only seems to happen in osci but either way it exposed that the service username for multi endpoints is constructed by iterating over the dictionary of settings from the remote unit and adding each service name to the service username. *2
The charm should not rely on the key order of an unordered object.
*1 https:/
*2 https:/
Changed in charm-keystone: | |
status: | New → Confirmed |
Changed in charm-nova-cloud-controller: | |
status: | New → Confirmed |
Changed in charm-keystone: | |
importance: | Undecided → Medium |
Changed in charm-nova-cloud-controller: | |
importance: | Undecided → Medium |
Changed in charm-keystone: | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in charm-nova-cloud-controller: | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in charm-keystone: | |
milestone: | none → 18.02 |
Changed in charm-nova-cloud-controller: | |
milestone: | none → 18.02 |
Changed in charm-neutron-gateway: | |
assignee: | nobody → Dmitrii Shcherbakov (dmitriis) |
status: | New → In Progress |
Changed in charm-neutron-gateway: | |
milestone: | none → 18.02 |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
Changed in charm-neutron-gateway: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/529316
Review: https:/