EL8 stackstorm is bundled with old PIP

[arm4b]

StackStorm v3.2.0. New RHEL8/CentOS8 has outdated pip 9.0.3 in its virtualenv:

[vagrant@centos8 ~]$ /opt/stackstorm/st2/bin/pip --version
pip 9.0.3 from /opt/stackstorm/st2/lib/python3.6/site-packages (python 3.6)

While others platforms are consistent with their pip version:

vagrant@ubuntu16:~$ /opt/stackstorm/st2/bin/pip --version
pip 19.1.1 from /opt/stackstorm/st2/local/lib/python2.7/site-packages/pip (python 2.7)

[vagrant@centos6 ~]$ /opt/stackstorm/st2/bin/pip --version
pip 19.1.1 from /opt/stackstorm/st2/lib/python2.7/site-packages/pip (python 2.7)

vagrant@ubuntu18:~$ /opt/stackstorm/st2/bin/pip --version
pip 19.1.1 from /opt/stackstorm/st2/lib/python3.6/site-packages/pip (python 3.6)

[punkrokk]

What is pip3 version?

…

Sent from my iPhone

On Apr 30, 2020, at 10:04 AM, Eugen C. ***@***.***> wrote:  StackStorm v3.2.0. New RHEL8/CentOS8 has outdated pip 9.0.3 in its virtualenv: ***@***.*** ~]$ /opt/stackstorm/st2/bin/pip --version pip 9.0.3 from /opt/stackstorm/st2/lib/python3.6/site-packages (python 3.6) While others platforms are consistent with their pip version: ***@***.***:~$ /opt/stackstorm/st2/bin/pip --version pip 19.1.1 from /opt/stackstorm/st2/local/lib/python2.7/site-packages/pip (python 2.7) ***@***.*** ~]$ /opt/stackstorm/st2/bin/pip --version pip 19.1.1 from /opt/stackstorm/st2/lib/python2.7/site-packages/pip (python 2.7) ***@***.***:~$ /opt/stackstorm/st2/bin/pip --version pip 19.1.1 from /opt/stackstorm/st2/lib/python3.6/site-packages/pip (python 3.6) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[nmaludy]

[vagrant@nickmaludy ~]$ cat /etc/redhat-release 
CentOS Linux release 8.0.1905 (Core) 
[vagrant@nickmaludy ~]$ pip3 --version
pip 20.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)
[vagrant@nickmaludy ~]$ /opt/stackstorm/st2/bin/pip3 --version
pip 9.0.3 from /opt/stackstorm/st2/lib/python3.6/site-packages (python 3.6)

[punkrokk]

@armab / @nmaludy any idea where this is set?

[arm4b]

Somewhere in the st2-packages. Definitely needs more debugging where old pip comes from during the packaging process.
Looking at the history here StackStorm/st2-packages#630 might help refreshing it in the memory.