Comment 1 for bug 1889071

I ran into this today, and it seems this is potentially a juju bug.

The principal charm, octavia, in my case, doesn't have a binding that maps to the space used by the ovn-chassis-octavia data binding.

For instance, octavia using all "oam-space" bindings, but ovn-chassis-octaiva using binding data=overlay-space, juju didn't configure the new octavia lxd (maas provider) with an overlay-space interface.

I would suggest that if juju knows about subordinates related to a new principal unit at deployment time (i.e, the subordinate relation is already defined in the model or bundle being deployed) it should also configure interfaces for subordinate charm space bindings.

Workaround in my case was to add a constraint to octavia: 'juju set-constraints octavia spaces=overlay-space' and then re-deploy octavia units.

My environment is running juju 2.8.7 model/agents.