charms.reactive changes force rework of defaults implementation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack AODH Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Barbican Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Designate Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Manila Charm |
Invalid
|
Undecided
|
Unassigned | ||
charms.openstack |
Fix Committed
|
Critical
|
Unassigned |
Bug Description
charms.reactive changed due to commit "Allow pluggable alternatives to RelationBase (#111)" (https:/
This only became apparent when debugging an issue on charm-manila and noticing that, although the handlers were being logged as being called, charms.reactive didn't actually call the handlers.
This means that the defaults that are defined in charms.openstack no longer work. There is a way to make them work, but it means moving the actual default handlers to layer-openstack and layer-openstack
This bug is used to track the behaviour and check that the default handlers work on all the reactive openstack charms.
Changed in charms.openstack: | |
assignee: | nobody → Alex Kavanagh (ajkavanagh) |
status: | New → In Progress |
Changed in charms.openstack: | |
assignee: | Alex Kavanagh (ajkavanagh) → nobody |
Fix proposed to branch: master /review. openstack. org/489565
Review: https:/