© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
confirmed the issue described in comment #4.
The root of the bug is there [0] where we set:
interpreter_python = auto
From the ansible docs [1]:
"Detects the target OS platform, distribution, and version, then consults a table listing the correct Python interpreter and path for each platform/
Since the jobs are on centos7 it decides that python2 is the right python for the ansible execution. However we are using python3 in those jobs.
With the patch at [2] I explicitly set the interpreter for get-hash to be python3. Test results at [3] are good. Centos7 at [4] and [5]
[4]
* 2021-09-22 11:43:29.960743 | primary | TASK [repo-setup : tripleo-get-hash current-tripleo for train on centos7 from https:/
* https:/
* 2021-09-22 11:43:29.960743 | primary | TASK [repo-setup : tripleo-get-hash current-tripleo for train on centos7 from https:/
* 2021-09-22 11:43:32.405325 | primary | TASK [repo-setup : tripleo-get-hash current for train on centos7 from https:/
* 2021-09-22 11:43:33.846358 | primary | ['the tq release is: train', 'the distro is: centos7', 'dlrn_hash is: c17c316f23f4589
[5]
* 2021-09-22 13:14:40.508154 | primary | TASK [repo-setup : tripleo-get-hash current-tripleo for train on centos7 from https:/
* 2021-09-22 13:14:43.754305 | primary | TASK [repo-setup : tripleo-get-hash current for train on centos7 from https:/
* 2021-09-22 13:14:45.160935 | primary | ['the tq release is: train', 'the distro is: centos7', 'dlrn_hash is: c17c316f23f4589
[0] https:/
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] https:/