I have a workaround/hack for it by force installing python2 pyyaml i will post a review for it but likely tomorrow so we can see if it is viable in the upstream ci then we can decide if we want to use it or not. we can also try to explicitly set the ansible_python_interpreter for the job
we are no longer blocked by this since we merged the partial revert in comment #3
poking a bit at this today, can reproduce on my local system.
Comes down to it installing pyyaml for python3, but then running the module with python2.
* https:/ /7e0affbd464b26 1bcc2a- f8803ca7587e43f 6b66c9edae98e76 0b.ssl. cf5.rackcdn. com/809427/ 2/gate/ tripleo- ci-centos- 7-containers- multinode/ cd5b7bd/ job-output. txt zuul/src/ opendev. org/openstack/ tripleo- ci/toci_ gate_test. sh:47): sudo /usr/bin/yum -y '--exclude= python2* ' install python3-setuptools python3-requests python3-urllib3 python3-PyYAML
* 2021-09-17 10:04:00.530959 | primary | +(/home/
I have a workaround/hack for it by force installing python2 pyyaml i will post a review for it but likely tomorrow so we can see if it is viable in the upstream ci then we can decide if we want to use it or not. we can also try to explicitly set the ansible_ python_ interpreter for the job
we can always just continue using the 'legacy' get hash for centos7 (i.e. https:/ /opendev. org/openstack/ tripleo- quickstart/ src/commit/ e16d99a2888c9cb 2461a3958eeebae 70d8e3cd4b/ roles/repo- setup/tasks/ get-dlrn- hash.yml# L16-L36 )