[Devstack] Unable to find pip2.7 ?
Dear all, It seems that there is a problem stacking Devstack using the master branch. The problem happens during the step: Installing package prerequisites [ERROR] /home/vagrant/devstack/inc/python:41 Unable to find pip2.7; cannot continue This is the minimum local.conf I used: [[local|localrc]] SERVICE_HOST=192.168.10.6 HOST_IP=192.168.10.6 HOST_IP_IFACE=eth1 DATABASE_PASSWORD=secretdatabase RABBIT_PASSWORD=secretrabbit ADMIN_PASSWORD=secretadmin SERVICE_PASSWORD=secretservice LOGFILE=$DEST/logs/stack.sh.log LOGDIR=$DEST/logs LOG_COLOR=False DEST=/opt/stack USE_PYTHON3=True As a workaround I need to revert the following change, then it ends up properly: commit 279a7589b03db69fd1b85d947cd0171dacef94ee Author: Jens Harbott (frickler) <j.harbott@x-ion.de> Date: Mon Apr 16 12:08:30 2018 +0000 Revert "Do not use pip 10 or higher" This reverts commit f99d1771ba1882dfbb69186212a197edae3ef02c. Added workarounds that might want to get split into their own patch before merging: - Don't install python-psutil - Don't run peakmem_tracker Change-Id: If4fb16555e15082a4d97cffdf3cfa608a682997d Any hints? -- Best regards, *Martín Chacón Pizá* *chacon.piza@gmail.com <chacon.piza@hotmail.com>*
This part of that change broke it: https://review.opendev.org/#/c/561597/21/tools/install_pip.sh since pip2 is no longer being installed when py3 is used. CI obviously hid the issue by having pip preinstalled. We should not really need pip2 now. -yoctozepto pt., 24 sty 2020 o 11:27 Martin Chacon Piza <chacon.piza@gmail.com> napisał(a):
Dear all,
It seems that there is a problem stacking Devstack using the master branch. The problem happens during the step: Installing package prerequisites [ERROR] /home/vagrant/devstack/inc/python:41 Unable to find pip2.7; cannot continue
This is the minimum local.conf I used:
[[local|localrc]] SERVICE_HOST=192.168.10.6 HOST_IP=192.168.10.6 HOST_IP_IFACE=eth1 DATABASE_PASSWORD=secretdatabase RABBIT_PASSWORD=secretrabbit ADMIN_PASSWORD=secretadmin SERVICE_PASSWORD=secretservice LOGFILE=$DEST/logs/stack.sh.log LOGDIR=$DEST/logs LOG_COLOR=False DEST=/opt/stack USE_PYTHON3=True
As a workaround I need to revert the following change, then it ends up properly:
commit 279a7589b03db69fd1b85d947cd0171dacef94ee Author: Jens Harbott (frickler) <j.harbott@x-ion.de> Date: Mon Apr 16 12:08:30 2018 +0000
Revert "Do not use pip 10 or higher"
This reverts commit f99d1771ba1882dfbb69186212a197edae3ef02c.
Added workarounds that might want to get split into their own patch before merging:
- Don't install python-psutil - Don't run peakmem_tracker
Change-Id: If4fb16555e15082a4d97cffdf3cfa608a682997d
Any hints?
-- Best regards, Martín Chacón Pizá chacon.piza@gmail.com
Proposed: https://review.opendev.org/704136 Please let us know if it helps there. -yoctozepto pt., 24 sty 2020 o 11:45 Radosław Piliszek <radoslaw.piliszek@gmail.com> napisał(a):
This part of that change broke it: https://review.opendev.org/#/c/561597/21/tools/install_pip.sh since pip2 is no longer being installed when py3 is used. CI obviously hid the issue by having pip preinstalled. We should not really need pip2 now.
-yoctozepto
pt., 24 sty 2020 o 11:27 Martin Chacon Piza <chacon.piza@gmail.com> napisał(a):
Dear all,
It seems that there is a problem stacking Devstack using the master branch. The problem happens during the step: Installing package prerequisites [ERROR] /home/vagrant/devstack/inc/python:41 Unable to find pip2.7; cannot continue
This is the minimum local.conf I used:
[[local|localrc]] SERVICE_HOST=192.168.10.6 HOST_IP=192.168.10.6 HOST_IP_IFACE=eth1 DATABASE_PASSWORD=secretdatabase RABBIT_PASSWORD=secretrabbit ADMIN_PASSWORD=secretadmin SERVICE_PASSWORD=secretservice LOGFILE=$DEST/logs/stack.sh.log LOGDIR=$DEST/logs LOG_COLOR=False DEST=/opt/stack USE_PYTHON3=True
As a workaround I need to revert the following change, then it ends up properly:
commit 279a7589b03db69fd1b85d947cd0171dacef94ee Author: Jens Harbott (frickler) <j.harbott@x-ion.de> Date: Mon Apr 16 12:08:30 2018 +0000
Revert "Do not use pip 10 or higher"
This reverts commit f99d1771ba1882dfbb69186212a197edae3ef02c.
Added workarounds that might want to get split into their own patch before merging:
- Don't install python-psutil - Don't run peakmem_tracker
Change-Id: If4fb16555e15082a4d97cffdf3cfa608a682997d
Any hints?
-- Best regards, Martín Chacón Pizá chacon.piza@gmail.com
Hi Radek, Thanks for the fast answer and the fix. We can stack it again. Best regards, Martin El vie., 24 de ene. de 2020 a la(s) 12:03, Radosław Piliszek ( radoslaw.piliszek@gmail.com) escribió:
Proposed: https://review.opendev.org/704136
Please let us know if it helps there.
-yoctozepto
pt., 24 sty 2020 o 11:45 Radosław Piliszek <radoslaw.piliszek@gmail.com> napisał(a):
This part of that change broke it: https://review.opendev.org/#/c/561597/21/tools/install_pip.sh since pip2 is no longer being installed when py3 is used. CI obviously hid the issue by having pip preinstalled. We should not really need pip2 now.
-yoctozepto
pt., 24 sty 2020 o 11:27 Martin Chacon Piza <chacon.piza@gmail.com>
Dear all,
It seems that there is a problem stacking Devstack using the master
branch.
The problem happens during the step: Installing package prerequisites [ERROR] /home/vagrant/devstack/inc/python:41 Unable to find pip2.7; cannot continue
This is the minimum local.conf I used:
[[local|localrc]] SERVICE_HOST=192.168.10.6 HOST_IP=192.168.10.6 HOST_IP_IFACE=eth1 DATABASE_PASSWORD=secretdatabase RABBIT_PASSWORD=secretrabbit ADMIN_PASSWORD=secretadmin SERVICE_PASSWORD=secretservice LOGFILE=$DEST/logs/stack.sh.log LOGDIR=$DEST/logs LOG_COLOR=False DEST=/opt/stack USE_PYTHON3=True
As a workaround I need to revert the following change, then it ends up
napisał(a): properly:
commit 279a7589b03db69fd1b85d947cd0171dacef94ee Author: Jens Harbott (frickler) <j.harbott@x-ion.de> Date: Mon Apr 16 12:08:30 2018 +0000
Revert "Do not use pip 10 or higher"
This reverts commit f99d1771ba1882dfbb69186212a197edae3ef02c.
Added workarounds that might want to get split into their own patch before merging:
- Don't install python-psutil - Don't run peakmem_tracker
Change-Id: If4fb16555e15082a4d97cffdf3cfa608a682997d
Any hints?
-- Best regards, Martín Chacón Pizá chacon.piza@gmail.com
-- *Martín Chacón Pizá* *chacon.piza@gmail.com <chacon.piza@hotmail.com>*
participants (2)
-
Martin Chacon Piza
-
Radosław Piliszek