Lead unit missing ovn config in octavia.conf

Bug #1916008 reported by Liam Young
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Octavia Charm
Fix Released
High
Liam Young

Bug Description

In an OVN deployment when the configure-resources action is run the lead unit will be missing OVN configuration from its octavia.conf but the other units will have it.

This is because the lead unit renders its configuration via a call to octavia_charm.render_all_configs in the action code, whereas the other units render their config inside a hook execution. Reactive interfaces based on charms.reactive.endpoints.Endpoints are supposed to register when the hook starts *1 but this is not called in an action. So when then render is called in an action the charms.reactive.endpoints.Endpoints appear to be missing.

*1 https://github.com/juju-solutions/charms.reactive/blob/master/charms/reactive/endpoints.py#L873

Liam Young (gnuoy)
Changed in charm-octavia:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Liam Young (gnuoy)
milestone: none → 21.04
Revision history for this message
Aurelien Lourot (aurelien-lourot) wrote :

I believed this has been fixed by gnuoy in https://github.com/openstack/charm-octavia/commit/073d33fe

Changed in charm-octavia:
status: Confirmed → Fix Committed
Changed in charm-octavia:
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.