OpenStack Designate Charm

The interface-memcached for 'request-restart' fails during the action 'openstack-upgrade'

Bug #1907857 reported by Alex Kavanagh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Designate Charm
Fix Released
Critical
Alex Kavanagh

Bug Description

Essentially, there is no scope during an action (in charms.reactive) so the typical way of setting the relation data on a RelationBase can't be used. Instead the conversations() iterator has to be used instead. This fix will be on the interface-memcached.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Bug raised in interface-memcached: https://github.com/omnivector-solutions/interface-memcache/issues/5

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Charm needs a rebuild. The associated interface-memcached bug has now been fixed and merged. https://github.com/omnivector-solutions/interface-memcache/pull/6

Changed in charm-designate:
status: New → In Progress
assignee: nobody → Alex Kavanagh (ajkavanagh)
importance: Undecided → High
importance: High → Critical
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

The stable version of the charm has been pushed with the included fix due to this review https://review.opendev.org/c/openstack/charm-designate/+/767140 which has merged; I've confirmed that it is in cs:designate-49

It will land in master with the next rebuild.

Changed in charm-designate:
status: In Progress → Won't Fix
status: Won't Fix → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.