ceph mon relation data behavior changed (ceph-radosgw amulet test failing)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ceph (Juju Charms Collection) |
Invalid
|
Undecided
|
Unassigned | ||
ceph-radosgw (Juju Charms Collection) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
ceph mon relation data behavior changed (ceph-radosgw amulet test failing)
I believe the following change to the ceph/next charm either broke ceph-radosgw, or at minimum changed the relation data that is present. Tests were passing on ceph-radosgw prior to this landing:
https:/
http://
If the new behavior is expected, the ceph-radosgw amulet tests need to be updated.
Here's what is observable in the ceph-radosgw test failure:
# Actual vs. Expected (manually exploded for readability):
2016-02-12 22:06:05,503 test_202_
2016-02-12 22:06:11,976 _validate_dict_data DEBUG: actual: {
u'private-address': u'10.5.0.33'
}
2016-02-12 22:06:11,976 _validate_dict_data DEBUG: expected: {
'private-address': <bound method OpenStackAmulet
'radosgw_key': <bound method OpenStackAmulet
'fsid': u'6547bd3e-
'ceph-public-
'auth': 'none'
}
description: | updated |
description: | updated |
description: | updated |
Changed in ceph (Juju Charms Collection): | |
status: | New → Invalid |
Changed in ceph-radosgw (Juju Charms Collection): | |
status: | New → Fix Committed |
milestone: | none → 16.04 |
tags: | added: openstack |
Changed in ceph-radosgw (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
I think that the change here is that the ceph / ceph-mon charm will now only set those configuration values on the leader, so the radosgw test needs to be updated to identify the leader and check configuration there. Also, this charm needs to be updated to use the new ceph-mon charm :)