IMHO, patching - is not a production way.

On Tue, May 23, 2023 at 3:11 PM Michal Arbet <michal.arbet@ultimum.io> wrote:

I am very glad that someone asked for an option to patch kolla images. 

I've already proposed patches for kolla here [1] and here [2]. 

But unfortunately I didn't get that many votes to merge into master and I abandoned this.

[1] https://review.opendev.org/c/openstack/kolla/+/829296

[2] https://review.opendev.org/c/openstack/kolla/+/829295

With these above patches you can patch files inside every container.

Maybe we can discuss this again ??

For example now xena, yoga, zed, antelope has oslo.messaging broken :

https://bugs.launchpad.net/oslo.messaging/+bug/2019978

fixed by

https://review.opendev.org/c/openstack/oslo.messaging/+/866617

As I am using my kolla patches in my downstream kolla git repo i've only created patches/ directory and place fix for openstack-base container :)

patches/
patches/openstack-base
patches/openstack-base/series
patches/openstack-base/fix-rabbitmq-issue-opendev-883538.patch

But, you still can use template-override https://docs.openstack.org/kolla/latest/admin/image-building.html .

Thanks

Michal Arbet
Openstack Engineer

Ultimum Technologies a.s.
Na Poříčí 1047/26, 11000 Praha 1
Czech Republic

+420 604 228 897 
michal.arbet@ultimum.io
https://ultimum.io

LinkedIn | Twitter | Facebook

st 17. 5. 2023 v 20:19 odesílatel Jeremy Stanley <fungi@yuggoth.org> napsal:

On 2023-05-17 21:02:02 +0300 (+0300), Maksim Malchuk wrote:
> Yes, you can do that, but note bene mitaka not supported.
[...]

Not only unsupported, but the stable/mitaka branch of
openstack/keystone was deleted when it reached EOL in 2017. You may
instead want to specify `reference = mitaka-eol` (assuming Git tags
also work there). That should get you the final state of the
stable/mitaka branch prior to its deletion.
--
Jeremy Stanley

--

Regards,

Maksim Malchuk