py27 and py35 jobs failing to setup tox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Critical
|
Al Bailey |
Bug Description
Brief Description
-----------------
In the last day or two, zuul jobs that invoke tox for py27 or py35 are failing during their setup phase.
This affects stx/fault, stx/config and perhaps other repos.
This blocks any reviews from passing zuul, and therefore all submissions are blocked from merging in those repos.
Severity
--------
Critical
Steps to Reproduce
------------------
Submit a code review in stx/fault
Expected Behavior
------------------
The review should pass zuul
Actual Behavior
----------------
Zuul fails to setup
ImportError: cannot import name 'ContextManager'
Reproducibility
---------------
Consistent
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
March 1, 2020
Last Pass
---------
Yes.
I triggered a recheck on a previously passing review and observed that it encountered the failure
https:/
Timestamp/Logs
--------------
py27 create: /home/zuul/
ERROR: invocation failed (exit code 1), logfile: /home/zuul/
=======
ImportError: cannot import name 'ContextManager'
=======
ERROR: InvocationError for command /usr/bin/python3 -m virtualenv --no-download --python /usr/bin/python2.7 py27 (exited with code 1)
Test Activity
-------------
Developer Submission
Workaround
----------
None, although I have verified the fix is to specify that 'bionic' nodeset instead of 'xenial' for the zuul job.
ie:
- nodeset: ubuntu-xenial
+ nodeset: ubuntu-bionic
Note: ubuntu-bionic nodes do not have python3.5. py35 targets should be converted to py36