Comment 10 for bug 1885936

Ah, but you may be on to something though. When Octavia is deployed with OVN and the `ovsb-cms` relation is added it enables both the traditional Amphora provider driver and the OVN provider driver.

For the OVN provider driver to work it requires the `octavia-driver-agent` to run and it communicates directly with the OVN central components. As you know the OVN central components require TLS to operate and expect its client to communicate over TLS to them. To avoid adding yet another TLS-related config to the Octavia charm it uses the certs provided to Apache when configuring the `octavia-driver-agent` for communicating with the OVN central components.

Looking at your topology you do have the `ovsdb-cms` relation but you do not have the `certificates` to Octavia.

Could you try either adding the `certificates` relation or removing the `ovsdb-cms` relation to/from the Octavia application?