Closed dor-abu closed 3 years ago
From what I understand the actionable here is to upgrade pip to latest version. I updated the Issue title to reflect it.
This is a st2 maintenance periodic task to update dependencies to latest versions and we'll try to use never pip
in the next st2 release.
@armab As you mentioned in slack, we updated virtualenv to 20.1.0 in st2actionrunner container
It solves the issue. When a pack is installed, it is installed with pip 20.2.4.
We are still checking for side effects.
Resolved by by changes committed to master under PR #5123. and related PRs.
Closing as upgraded pip in v3.5.0.
how can we update pip for the kubernetes deployment of ST2?
SUMMARY
A few days ago packs that had aio-pika in requirements failed in "install pack dependencies" phase.
We found out that aio-pika uses yarl as a requirement without a fixed version. yarl pushed changes to master in recent days, and also uses multidict who also created changes in recent days.
We resolved the issue when we manually updated the version of pip to latest - 20.2.3.
STACKSTORM VERSION
st2 3.1.0, on Python 3.6.9
OS, environment, install method
We uses Docker and custom docker-compose.
Steps to reproduce the problem
Insert yarl, aio-pika, or multidict to requirements with pip version 19.1.1 in the virtual environment of the packages
Expected Results
We expect to pass the phase of "install pack dependencies".
Actual Results
This error will be raised: