i belive michael still just proposed a fix for this
https://review.opendev.org/c/openstack/kolla/+/967475

at least for debian to address https://bugs.launchpad.net/kolla/+bug/2131736

im not sure if similar repos exist for jammy

mikal's patch adresses bookworm and noble since those are the currently
supproted distros
on master. that will obviously need to be backported to current stable
banches but 2023.1 is now technically
unmaintained and  should be moving to EOL so min not sure htat the fix
will be backporte that far.

im getting cloudflay errrors form https://deb1.rabbitmq.com/ so i cant
check if there is a
https://deb1.rabbitmq.com/rabbitmq-server/ubuntu/jammy" but if there is
backporting mikal's fix after its landed and
updating it to jamy when the supproted release chagne form noble to
jammy is proably the correct approch.

in general however i woudl advice plannign you upgrade form 2023.1 to
2025.1 or at least 2024.1 to move to a supported release.
2023.1 is not getting secuirty updates and 2024.1 is already moved to
unmaintaiend so you really shoudl try and move to 2025.1
as soon as resonably possible for your deployment.

regards
sean


On 17/11/2025 22:08, Rob Jefferson wrote:
> Folks,
>
> At work, we're using Kolla 2023.1, and during a recent build, I saw
> that the PPA that provided RabbitMQ packages gave me a "402 Payment
> Required" error. This seems to be an existing problem, so I decided to
> try using the PPA that's in the current version of 2023.1 Kolla. When
> I change the repo in `kolla/templates/repos.yml` so that the URL is
>
> https://ppa1.rabbitmq.com/rabbitmq/rabbitmq-server/deb/ubuntu
>
> and the key in `docker/base/Dockerfile.j2` to be 9F4587F226208342, I
> get the following error:
>
>> E: The repository 'https://ppa1.rabbitmq.com/rabbitmq/rabbitmq-server/deb/ubuntu jammy Release' does not have a Release file.
> If, on the other hand, I use the PPA in the official RabbitMQ docs:
>
> https://deb1.rabbitmq.com/rabbitmq-erlang/ubuntu/jammy
>
> And use the key 0A9AF2115F4687BD29803A206B73A36E6026DFCA, I get the
> following error:
>
>> W: GPG error: https://deb1.rabbitmq.com/rabbitmq-server/ubuntu/jammy jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B73A36E6026DFCA
>> INFO:kolla.common.utils.rabbitmq:E: The repository 'https://deb1.rabbitmq.com/rabbitmq-server/ubuntu/jammy jammy InRelease' is not signed.
> In both cases, I'm not sure what the issue is. I would have expected
> RabbitMQ server for Jammy to still be available in the first case
> (especially since that PPA remains in Kolla), or for the key I used in
> the second case to exist.
>
> Is there something I can try to fix this issue?
>
> Thanks,
>
> Rob
>