Hi all,

Is there any way, how I could modify [0] so tripleO would not download again my modified image? Or could it be fixed? Should I raise bug report? is it in the launchpad again? Should it be for Horizon or for TripleO or Kolla?

And yes, i understand that it tries to use python exec instead of python3 exec ;) but I am completely new in containerized setup, how to modify it "by hand" so TripleO deployment would not fix it back, and either way, if might be not working for more people, or it works for others?! And only me who is facing this issue?

[0] https://github.com/openstack/kolla/blob/12905b5fc18c93fdece91df9a2446771d10dfbad/docker/horizon/extend_start.sh#L18 ?

On Thu, 16 Jul 2020 at 10:38, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:

Hi all,

I have noticed, that horizon container fails to start and some interestin zen_wozniak has apeared [0].
Healthcheck log is empty, but horizon log [1] sais "/usr/bin/python: No such file or directory" and there is no such file or directory :)

after sume update it failed. I believe you guys will push update fast enough, as I am still bad at this git and container part....
HOW to fix it now :) on my side? As tripleo will redeploy horizon from images... and will update image. could you please give me a hint where to duck tape it whille it will be pushed to prod?

[0] http://paste.openstack.org/show/3jjnsgXfWRxs3o0G6aKH/
[1] http://paste.openstack.org/show/1S66A55cz0UaFUWGxID8/
--
Ruslanas Gžibovskis
+370 6030 7030