<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/kolla/docker/rabbitmq/Dockerfile.j2, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=master</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2026-08-05T08:13:09+00:00</updated>
<entry>
<title>Add cleanup_repos to revert build_only overrides</title>
<updated>2026-08-05T08:13:09+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-06-17T05:24:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=5aabec47f057d9cb32aab520d666e51bd9ee37c6'/>
<id>urn:sha1:5aabec47f057d9cb32aab520d666e51bd9ee37c6</id>
<content type='text'>
Repos marked build_only: true are backed up before handle_repos()
overwrites them and restored at the end of each image build, so CI
mirror URLs are not baked into the final image.

The cleanup RUN was injected into every Dockerfile, not just images
that called handle_repos() for those repos. Child images with no
backup fell through to "rm -f", deleting the inherited repo file
(e.g. debian.sources in bifrost-base, breaking cpio install).

Fix by adding a {repo}.enabled sentinel that handle_repos creates
when it processes a build_only repo, making the cleanup conditional
on that sentinel.

Change-Id: Ie5b9970a4575b6258dc238059d3f33ddfe155789
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>rabbitmq: Update to 4.3</title>
<updated>2026-07-20T16:11:43+00:00</updated>
<author>
<name>Piotr Milewski</name>
<email>vurmil@gmail.com</email>
</author>
<published>2026-05-13T10:53:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=78a06e4e973ad32fbe04606b861fa5864f588c0d'/>
<id>urn:sha1:78a06e4e973ad32fbe04606b861fa5864f588c0d</id>
<content type='text'>
Erlang 28 is only supported for new clusters. Upgrades of clusters
running RabbitMQ with Khepri on Erlang 27 to Erlang 28 have a known
issue affecting rolling upgrades.

Change-Id: I60d85a92534e8aa9ec6a72d71457057b96d7e554
Signed-off-by: Piotr Milewski &lt;vurmil@gmail.com&gt;
</content>
</entry>
<entry>
<title>Migrate to pyproject.toml</title>
<updated>2026-07-06T19:59:40+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-07-06T13:26:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=db35ac8d793506bc43b62e7e39d27a75de1043ed'/>
<id>urn:sha1:db35ac8d793506bc43b62e7e39d27a75de1043ed</id>
<content type='text'>
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.

Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.

Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
</feed>
