Thank you Sven,

I totally agreed about building images but in my case I have recipe to recompile existing image with inserting patch. It’s not a best practice but it does work and I did patch couple of images in past. 

Sure I can wait and no rush only reason to open this thread for reference so it helps others also. In IRC things get buried. 

Thanks for the help. 

On Wed, May 22, 2024 at 8:19 AM Sven Kieske <kieske@osism.tech> wrote:

Hi,

we are currently working on an upstream workaround, see the bug report
(patches should show up there soon, once the bot picks them up):

https://bugs.launchpad.net/kolla-ansible/+bug/2066364

we need to fix this in multiple repositories (kolla-ansible, ansible-
collection-kolla at least) and on multiple branches as well to make
SLURP upgrade jobs green again, so please have some patience, it should
be sorted out soon(TM).

See these patches for the work in progress:

https://review.opendev.org/c/openstack/ansible-collection-kolla/+/920124
https://review.opendev.org/c/openstack/ansible-collection-kolla/+/920125
https://review.opendev.org/c/openstack/kolla-ansible/+/920169

As I mentioned yesterday on IRC it is recommended to build your own
images. If you don't do this, you can't easily control what ends up
in your deployed images and you must wait until we fix the upstream
bugs, which does take more time in this case, because we need to
account for upgrade tests gating our CI pipeline, which you probably
don't need in your downstream CI.

Thanks

--
Sven Kieske
Senior Cloud Engineer

Mail: kieske@osism.tech
Web: https://osism.tech

OSISM GmbH
Teckstraße 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139