Patch[0] brought the issue to notice as we changed that playbook to use the ansible controller interpreter rather than discovering it.
For now, we can merge patches [1] and [2] and look at if there is a case to use venv later. If we plan to use venv for some reason ( we should install all python libraries using pip). But we don't use virtual env for content provider jobs[3].
Thanks to Rabi and Takashi for the fix.
Testproject: https:/ /review. rdoproject. org/r/c/ testproject/ +/25325/ 125/.zuul. yaml#7 is green var "buildcontainer s_venv: false"
https:/ /logserver. rdoproject. org/25/ 25325/125/ check/periodic- tripleo- ci-build- containers- ubi-9-quay- push-master/ e519ee1/ logs/build_ containers. sh confirms no virtual env used.
Adding a summary of the discussion with Rabi:
Patch[0] brought the issue to notice as we changed that playbook to use the ansible controller interpreter rather than discovering it.
For now, we can merge patches [1] and [2] and look at if there is a case to use venv later. If we plan to use venv for some reason ( we should install all python libraries using pip). But we don't use virtual env for content provider jobs[3].
Rabi plans to cherry-pick [1] at least till Zed.
[0] https:/ /review. opendev. org/c/openstack /python- tripleoclient/ +/864647/ 3/tripleoclient /v2/tripleo_ container_ image.py /review. rdoproject. org/r/c/ config/ +/46139 /review. rdoproject. org/r/c/ rdo-jobs/ +/46141 /c18ded86635bab 17724f- 51fb74e788bc28a 37082204769947c 3c.ssl. cf1.rackcdn. com/periodic/ opendev. org/openstack/ tripleo- heat-templates/ master/ tripleo- ci-centos- 9-content- provider/ 3352f61/ logs/undercloud /home/zuul/ tripleo_ container_ image_build. sh
[1] https:/
[2] https:/
[3] https:/