The lb's with multiple listeners for different ports as created by k8s
(for helm deployed istio) still drop into an error state.
The lb created by k8s for a lb with a single listener (for helm deployed
jenkins) still work fine as before
--
You received this bug notification because you are a mem
** Attachment added: "output of loadbalancer status show for each"
https://bugs.launchpad.net/snap-openstack/+bug/2091931/+attachment/5851646/+files/lb-status.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Applying ppa from http://ppa.launchpadcontent.net/james-page/caracal did
not resurrect an errored LB, nor did it allow a newly created lb to fall
into this state.
** Attachment added: "Screenshot from 2025-01-14 14-04-28.png"
https://bugs.launchpad.net/snap-openstack/+bug/2091931/+attachment/5
Can confirm after testing on 2024.1/edge (644) that with this patchset
applied that magnum conductor error logs are clean, magnum conductor is
stable as of 25 mins ago. Previously multiple restarts would be seen in
a 10min time frame especially during coe cluster create.
--
You received this bug
Heat state is updated into magnum quickly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089581
Title:
[CaaS] magnum-conductor in down state
To manage notifications about this bug go to:
https://bu
** Attachment added: "Patch applied and running from 16:43"
https://bugs.launchpad.net/snap-openstack/+bug/2089581/+attachment/5850667/+files/magnum-conductor.logs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Attachment added: "Horizon dashboard magnum view of cluster showing complete
and healthy"
https://bugs.launchpad.net/snap-openstack/+bug/2089581/+attachment/5850668/+files/Screenshot%20from%202025-01-09%2017-14-18.png
--
You received this bug notification because you are a member of Ubunt
Suggested to try applying https://bugs.launchpad.net/magnum/+bug/2067345
to see if this resolves general noble/python3.12 issues.
Initial attempt seems to clear the errors once osprofiler was forcibly
pip installed.
That said, cannot give thumbs up to this as functionality could not be tested
(
