[kolla-ansible] How to pin pip3 module in kolla-ansible
Folks, I have deployed kolla-ansible using public images so far everything is good until I hit this bug [1] requests pip module had a minor bug. Now my question is if I want to pin requests==2.31.0 version in kolla-ansible then what file should I be adding to the pin version? This is not an image building related module because it deployed on a metal host so nothing to do with building kolla images. It's a pure docker issue. 1. https://github.com/docker/docker-py/pull/3257
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
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 <https://www.google.com/maps/search/Teckstra%C3%9Fe+62+%2F+70190+Stuttgart+%2F+Deutschland?entry=gmail&source=g>
Geschäftsführer: Christian Berendt Unternehmenssitz: Stuttgart Amtsgericht: Stuttgart, HRB 756139
I have the same question. If we want to install a package to all images, we will add it to ubuntu base image, right? On Wed, May 22, 2024, 7:35 PM Satish Patel <satish.txt@gmail.com> wrote:
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 <https://www.google.com/maps/search/Teckstra%C3%9Fe+62+%2F+70190+Stuttgart+%2F+Deutschland?entry=gmail&source=g>
Geschäftsführer: Christian Berendt Unternehmenssitz: Stuttgart Amtsgericht: Stuttgart, HRB 756139
participants (3)
-
Nguyễn Hữu Khôi
-
Satish Patel
-
Sven Kieske