identity-admin relation: if admin-password not set, service_password=None when running unclustered
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Keystone Charm |
Triaged
|
Medium
|
Unassigned | ||
keystone (Juju Charms Collection) |
Invalid
|
Medium
|
Unassigned |
Bug Description
If keystone (revno=157) is deployed as suggested (w/o setting admin-password parameter), related service does not receive service_password value.
ie:
juju add-relation myservice "keystone:
"""
settings(
u'service_region': u'RegionOne', u'service_
u'service_port': u'5000', u'private-address': u'10.55.60.119',
u'service_
u'service_
}
"""
However, if I juju set keystone admin-password=
ie:
juju set keystone admin-password=
juju add-relation myservice "keystone:
"""
settings(
u'service_region': u'RegionOne', u'service_
u'service_port': u'5000', u'private-address': u'10.55.60.119',
u'service_
u'service_
}
"""
I read lp#1385105 and I think it is slightly different to described behaviour here.
Cheers,
-Alvaro.
Changed in charm-keystone: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in keystone (Juju Charms Collection): | |
status: | Triaged → Invalid |
I see the issue here:
if is_relation_ made("cluster" ): 'admin_ passwd' )
store_ admin_passwd( passwd)
passwd = peer_retrieve(
if passwd:
return passwd
is_relation_made relies on at least one other unit being part of a relation - I suspect that you may be deploying a standalone keystone, in which case this check is false, and the function just returns the default None value from an earlier config call in the get_admin_passwd function.
TBH that entire function needs refactoring to use leader-storage.