Question about patch to fix problem
Hello, A few days ago, I asked a question about applying a patch to resolve a problem in my OpenStack environment. I didn't get a response. My question was probably stupid and not appropriate for this list. I apologize. Having to resolve this problem, I searched high and low using search engines. It seems that the solution, with kolla-ansible, is to upgrade to Epoxy, which takes the patch into account. Since this update could cause other problems, I don't want to do it for the moment. Is there another solution? Is it possible to modify the code (it's simply a line to modify in a file (https://review.opendev.org/c/openstack/horizon/+/942946)) in the two Horizon containers in my cluster? I'm really sorry if this is a stupid question, but I've been searching and can't find a method for applying these patches. Franck
Hello Franck, The change you listed is a cherry pick (backport) of the Bugfix to Dalmatian (2024.2). What release are you on right now? It might be as simple as waiting till this merges (looks like very soon) and bumping just the Horizon containers, no Epoxy upgrade necessary If you're really in a hurry you would have to resolve to cherry picking it locally and building the containers yourself locally. Best regards, *Jakub Darmach* On Thu, 10 Apr 2025 at 09:42, Franck VEDEL (UGA) < franck.vedel@univ-grenoble-alpes.fr> wrote:
Hello, A few days ago, I asked a question about applying a patch to resolve a problem in my OpenStack environment. I didn't get a response. My question was probably stupid and not appropriate for this list. I apologize. Having to resolve this problem, I searched high and low using search engines. It seems that the solution, with kolla-ansible, is to upgrade to Epoxy, which takes the patch into account. Since this update could cause other problems, I don't want to do it for the moment. Is there another solution? Is it possible to modify the code (it's simply a line to modify in a file ( https://review.opendev.org/c/openstack/horizon/+/942946)) in the two Horizon containers in my cluster? I'm really sorry if this is a stupid question, but I've been searching and can't find a method for applying these patches.
Franck
Hello Jakub, Thanks for your help. I’m not hurry, Since I want to understand more about how this all works and how to apply fixes, I don't want to update with Epxy. So I'll wait a bit. Thanks for all the information. Franck
Le 10 avr. 2025 à 09:59, Jakub Darmach <jakub.darmach@gmail.com> a écrit :
Hello Franck, The change you listed is a cherry pick (backport) of the Bugfix to Dalmatian (2024.2). What release are you on right now? It might be as simple as waiting till this merges (looks like very soon) and bumping just the Horizon containers, no Epoxy upgrade necessary
If you're really in a hurry you would have to resolve to cherry picking it locally and building the containers yourself locally.
Best regards, Jakub Darmach
On Thu, 10 Apr 2025 at 09:42, Franck VEDEL (UGA) <franck.vedel@univ-grenoble-alpes.fr <mailto:franck.vedel@univ-grenoble-alpes.fr>> wrote:
Hello, A few days ago, I asked a question about applying a patch to resolve a problem in my OpenStack environment. I didn't get a response. My question was probably stupid and not appropriate for this list. I apologize. Having to resolve this problem, I searched high and low using search engines. It seems that the solution, with kolla-ansible, is to upgrade to Epoxy, which takes the patch into account. Since this update could cause other problems, I don't want to do it for the moment. Is there another solution? Is it possible to modify the code (it's simply a line to modify in a file (https://review.opendev.org/c/openstack/horizon/+/942946)) in the two Horizon containers in my cluster? I'm really sorry if this is a stupid question, but I've been searching and can't find a method for applying these patches.
Franck
Hello Franck, Glad to help - and welcome to the community! Regards, Jakub Best regards, Jakub Darmach On Thu, Apr 10, 2025, 13:28 Franck VEDEL (UGA) < franck.vedel@univ-grenoble-alpes.fr> wrote:
Hello Jakub, Thanks for your help. I’m not hurry, Since I want to understand more about how this all works and how to apply fixes, I don't want to update with Epxy. So I'll wait a bit.
Thanks for all the information.
Franck
Le 10 avr. 2025 à 09:59, Jakub Darmach <jakub.darmach@gmail.com> a écrit :
Hello Franck, The change you listed is a cherry pick (backport) of the Bugfix to Dalmatian (2024.2). What release are you on right now? It might be as simple as waiting till this merges (looks like very soon) and bumping just the Horizon containers, no Epoxy upgrade necessary
If you're really in a hurry you would have to resolve to cherry picking it locally and building the containers yourself locally.
Best regards, *Jakub Darmach*
On Thu, 10 Apr 2025 at 09:42, Franck VEDEL (UGA) < franck.vedel@univ-grenoble-alpes.fr> wrote:
Hello, A few days ago, I asked a question about applying a patch to resolve a problem in my OpenStack environment. I didn't get a response. My question was probably stupid and not appropriate for this list. I apologize. Having to resolve this problem, I searched high and low using search engines. It seems that the solution, with kolla-ansible, is to upgrade to Epoxy, which takes the patch into account. Since this update could cause other problems, I don't want to do it for the moment. Is there another solution? Is it possible to modify the code (it's simply a line to modify in a file ( https://review.opendev.org/c/openstack/horizon/+/942946)) in the two Horizon containers in my cluster? I'm really sorry if this is a stupid question, but I've been searching and can't find a method for applying these patches.
Franck
Hi Franck, What you could do is to build your own image with the code changes. You can cherry-pick the commit or just apply it manually. Here in kolla-ansible docs[1] you can see how to build images with kolla-build, and here[2] you can check how to specify the built image. Could be useful for you [1] https://docs.openstack.org/kolla/latest/admin/image-building.html [2] https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/horizon... Best regards. On Thu, Apr 10, 2025, 04:42 Franck VEDEL (UGA) < franck.vedel@univ-grenoble-alpes.fr> wrote:
Hello, A few days ago, I asked a question about applying a patch to resolve a problem in my OpenStack environment. I didn't get a response. My question was probably stupid and not appropriate for this list. I apologize. Having to resolve this problem, I searched high and low using search engines. It seems that the solution, with kolla-ansible, is to upgrade to Epoxy, which takes the patch into account. Since this update could cause other problems, I don't want to do it for the moment. Is there another solution? Is it possible to modify the code (it's simply a line to modify in a file ( https://review.opendev.org/c/openstack/horizon/+/942946)) in the two Horizon containers in my cluster? I'm really sorry if this is a stupid question, but I've been searching and can't find a method for applying these patches.
Franck
On 2025-04-10 09:46:07 -0300 (-0300), Winicius Allan wrote:
What you could do is to build your own image [...]
This is highly encouraged for production systems and other sensitive deployments regardless. The OpenStack community does not have resources to track or manage problems like security vulnerabilities in the various non-OpenStack software contained in these images, and the container images published by the community are therefore meant as examples for testing and non-critical prototyping. The frozen dependency constraints on stable OpenStack branches are going to fall progressively out of date as time moves forward, and this is intentional as they're a snapshot in time for the purposes of stabilizing upstream testing processes; these frozen dependency versions will accumulate more and more known vulnerabilities over time. Production deployments should be done with images you build and test, using versions of dependencies you track and audit for potential security risks so that you can directly mitigate or patch them accordingly. -- Jeremy Stanley
On 10/4/25, 15:22, "Jeremy Stanley" <fungi@yuggoth.org> wrote: On 2025-04-10 09:46:07 -0300 (-0300), Winicius Allan wrote:
What you could do is to build your own image [...]
This is highly encouraged for production systems and other sensitive deployments regardless. The OpenStack community does not have resources to track or manage problems like security vulnerabilities in the various non-OpenStack software contained in these images, and the container images published by the community are therefore meant as examples for testing and non-critical prototyping. The frozen dependency constraints on stable OpenStack branches are going to fall progressively out of date as time moves forward, and this is intentional as they're a snapshot in time for the purposes of stabilizing upstream testing processes; these frozen dependency versions will accumulate more and more known vulnerabilities over time. Production deployments should be done with images you build and test, using versions of dependencies you track and audit for potential security risks so that you can directly mitigate or patch them accordingly. Thanks for this clear explanation, Jeremy. This is something that everyone using OpenStack in production must be aware of. Best regards, Alberto
Hi Allan. Thanks a lot. I've never needed all of this before, and I hadn't seen the information provided in these links. I think this will be a great help, even though I don't think it's going to be easy to use at first. Thank you again for this invaluable help. Franck
Le 10 avr. 2025 à 14:46, Winicius Allan <winiciusab12@gmail.com> a écrit :
Hi Franck,
What you could do is to build your own image with the code changes. You can cherry-pick the commit or just apply it manually. Here in kolla-ansible docs[1] you can see how to build images with kolla-build, and here[2] you can check how to specify the built image. Could be useful for you
Glad to help! If you need more help, let me know. Em qui., 10 de abr. de 2025 às 16:09, Franck VEDEL (UGA) < franck.vedel@univ-grenoble-alpes.fr> escreveu:
Hi Allan. Thanks a lot. I've never needed all of this before, and I hadn't seen the information provided in these links. I think this will be a great help, even though I don't think it's going to be easy to use at first. Thank you again for this invaluable help.
Franck
Le 10 avr. 2025 à 14:46, Winicius Allan <winiciusab12@gmail.com> a écrit :
Hi Franck,
What you could do is to build your own image with the code changes. You can cherry-pick the commit or just apply it manually. Here in kolla-ansible docs[1] you can see how to build images with kolla-build, and here[2] you can check how to specify the built image. Could be useful for you
participants (5)
-
Alberto Molina Coballes
-
Franck VEDEL (UGA)
-
Jakub Darmach
-
Jeremy Stanley
-
Winicius Allan