[2023.1][kolla][rabbitmq] Failing to get packages from RabbitMQ Repos
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
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
It does exist for jammy on deb1/2 just in case On Tue, 18 Nov 2025, 13:03 Sean Mooney, <smooney@redhat.com> wrote:
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
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
On 17/11/2025 22:08, Rob Jefferson wrote: 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
Heya, 2025.1 and master are definitely broken. I would expect _any_ version to be broken, but haven't explicitly checked. Given 2023.1 is out of support, I think you'd need to backport https://review.opendev.org/c/openstack/kolla/+/967475, the problem being it can be a bit fiddly to test. Once the gerrit review is merged (and the plan therefore finalized), I can try to give you a hand with a backport if you want. You'd need tooling to be able to carry the patch yourself though I think, although I assume if you're doing private image builds you probably already have that. Michael On Tue, Nov 18, 2025 at 11:05 PM Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
It does exist for jammy on deb1/2 just in case
On Tue, 18 Nov 2025, 13:03 Sean Mooney, <smooney@redhat.com> wrote:
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
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
On 17/11/2025 22:08, Rob Jefferson wrote: 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
Just wanted to update. Michael, I did a quick test of the backport on 2023.1, using Jammy instead. Got some 500 issues (probably related to cloudflare's outage this morning), but a second test later was fine. I can turn the changes into a local patch and use that privately. As much as I'd love to upgrade to 2025.1 (or even 2024.1), that's more of a "someday" thing. For now, we've been handling selected backports and other patches in our environment. Thanks, all! Rob On Tue, Nov 18, 2025 at 2:05 PM Michael Still <mikal@stillhq.com> wrote:
Heya,
2025.1 and master are definitely broken. I would expect _any_ version to be broken, but haven't explicitly checked.
Given 2023.1 is out of support, I think you'd need to backport https://review.opendev.org/c/openstack/kolla/+/967475, the problem being it can be a bit fiddly to test. Once the gerrit review is merged (and the plan therefore finalized), I can try to give you a hand with a backport if you want. You'd need tooling to be able to carry the patch yourself though I think, although I assume if you're doing private image builds you probably already have that.
Michael
On Tue, Nov 18, 2025 at 11:05 PM Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
It does exist for jammy on deb1/2 just in case
On Tue, 18 Nov 2025, 13:03 Sean Mooney, <smooney@redhat.com> wrote:
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
participants (4)
-
Dmitriy Rabotyagov
-
Michael Still
-
Rob Jefferson
-
Sean Mooney