The problem is that the Octavia units go into an error state during deployment after Vault is initialized but before Octavia is initialized. The expected behaviour is that the Octavia units do not go into an error state. A more detailed overview of the symptoms can be found in the first comment.
An overview of the versions used can be found in the first link, but for completeness:
====== 0ubuntu0~ 22.04.1 yoga-jammy 0landscape0
maas - 3.2.8-
juju - 2.9.44
cpe-foundation - 2.21
infra-ubuntu - focal
ceph - quincy/stable
openstack-charms - yoga/stable
charmed-kubernetes - 1.27
cloud-init - 23.2.1-
fce-container-image - ubuntu:jammy
openstack - yoga
sku - fcb-master-
legacy-lma - latest/candidate
solutions-qa-ci - d0ba8ed0
landscape-server - 23.03+16-
cos-lite - latest/stable:11
fcbtest - latest/beta
======
Our environment is using a persistent Maas 3.2.8 deployment with a juju 2.9.44 controller bootstrapped and an OpenStack bundle (https:/ /oil-jenkins. canonical. com/artifacts/ 1d6752e4- e03a-476f- 9f5b-d4de9e1e17 2d/generated/ generated/ openstack/ bundle. yaml) deployed.
The problem is that the Octavia units go into an error state during deployment after Vault is initialized but before Octavia is initialized. The expected behaviour is that the Octavia units do not go into an error state. A more detailed overview of the symptoms can be found in the first comment.