Comment 1 for bug 1946325

Hello Radu,

I just hit a similar issue and have spent some time looking at this.

It looks like there's been a bug fix for a different bug, https://bugs.launchpad.net/charm-octavia/+bug/1893446, which will cause the octavia units to go into a blocked state if the port isn't set up right. That's in the stable/21.10 release of the OpenStack charms, which would currently mean cs:octavia-37.

This caused me to review code and docs a bit, and it seems to me like we both may want to run the configure-resources action. Quoting from the charm's README:

> By executing the configure-resources action the charm will create the resources required for operation of the Octavia service. If you want to manage these resources yourself you must set the create-mgmt-network configuration option to False.
>
> You can at any time use the configure-resources action to prompt immediate resource discovery.

Hope this helps; I'm going to see if we can run this on my side to resolve the issue.

Best Regards,
Paul Goins