Upgrade pip2 after upgrading pip3 #5743
Merged
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrading pip3 after pip2 caused the
pip
command to be aliased to thepip3
command. However, since we are still transitioning from Python 2 to Python 3, mostpip
commands in the codebase are expectingpip
to alias topip2
. The proper solution here is to explicitly callpip2
andpip3
, and no longer callpip
, however this will require extensive changes and testing, so to quickly fix this issue, we upgraded pip2 after pip3 to ensure that pip2 is installed after pip3.- Why I did it
Fix issues introduced via #5656
- How I did it
Upgrade pip2 after pip3 in slave containers and config engine container.
- How to verify it
Ensure image builds are all containers start properly
- Which release branch to backport (provide reason below if selected)