ceph mon relation data behavior changed (ceph-radosgw amulet test failing)

Bug #1545179 reported by Ryan Beisner
6
This bug affects 1 person
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://code.launchpad.net/~hopem/charms/trusty/ceph/lp1476749/+merge/282167
http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/ceph/next/revision/130

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_ceph1_ceph_radosgw_relation DEBUG: Checking ceph1:radosgw ceph-radosgw:mon relation data...

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 OpenStackAmuletUtils.valid_ip of <charmhelpers.contrib.openstack.amulet.utils.OpenStackAmuletUtils object at 0x7f798c4a3250>>,

'radosgw_key': <bound method OpenStackAmuletUtils.not_null of <charmhelpers.contrib.openstack.amulet.utils.OpenStackAmuletUtils object at 0x7f798c4a3250>>,

'fsid': u'6547bd3e-1397-11e2-82e5-53567c8d32dc',

'ceph-public-address': <bound method OpenStackAmuletUtils.valid_ip of <charmhelpers.contrib.openstack.amulet.utils.OpenStackAmuletUtils object at 0x7f798c4a3250>>,

'auth': 'none'
}

Ryan Beisner (1chb1n)
description: updated
description: updated
Ryan Beisner (1chb1n)
description: updated
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

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 :)

Revision history for this message
Edward Hope-Morley (hopem) wrote :

fwiw i have resolved this issue as part of another merge proposal - https://code.launchpad.net/~hopem/charms/trusty/ceph-radosgw/lp1513524/+merge/285808

Revision history for this message
Ryan Beisner (1chb1n) wrote :

FYI @chris.macnaughton - we will only update amulet test topologies for neighboring charms after ceph-mon hits ~openstack-charmers proper.

James Page (james-page)
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
James Page (james-page)
Changed in ceph-radosgw (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.