-
Notifications
You must be signed in to change notification settings - Fork 108
Error executing action install
on resource 'python_package[setuptools]'
#133
Comments
https://pypi.org/project/pip/#history shows 18.1 was released a couple hours ago. Rolling back to 18.0 via |
Interestingly enough. Does not impact CentOS 6.x but does impact CentOS 7.x |
Doing
does not work because of pypa/pip#5857 which is probably the cause of original issue, given that they occurred at the same time. |
Any workaround we can implement into the actual cookbook? |
You can try setting the |
This works for me: python_runtime '3' do
get_pip_url 'https://github.com/pypa/get-pip/raw/f88ab195ecdf2f0001ed21443e247fb32265cabb/get-pip.py'
pip_version '18.0'
end |
Hopefully this will be fixed upstream shortly. I'll monitor the upstream ticket and see how it goes. |
I am getting the same thing for python_runtime '2', any tips for this? plz and ty! |
@aungger Same fix, the current default |
if your dependency on poise-python is through a wrapped cookbook and you can't change the pip_version or get_pip_url parameters of the resource... we had success implementing the following workaround in our wrapper cookbook:
|
If you're using a virtualenv resource, you also needed to set the
|
Update: They merged a fix to get-pip but it seems to only resolve the part where
works now, but blows up without the |
confirmed, overriding the attribute will force poise-python to use pip 18.0 and our cookbooks now work as expected
|
It [moved](pypa/pip@a5a07fe) the from_line method in a backwards-incompatible way. This should resolve the remainder of poise#133. My Python is pretty atrophied, but I tested this against the following recipe and it converged successfully. ```ruby apt_update 'default' python_runtime '2' python_virtualenv '/tmp/piplatest' do python '2' end python_virtualenv '/tmp/pip18' do python '2' pip_version '18.0' end python_virtualenv '/tmp/pip10' do python '2' pip_version '10.0.1' end python_virtualenv '/tmp/pip9' do python '2' pip_version '9.0.3' end ```
This issue still appears in wrapper cookbook. |
python_runtime '3' failing on ubuntu 18
` |
@lopezm1 Good find! This was the quickest and easiest way to get around this error for me. |
I was having this issue if a previous chef run was cached. Have you tried clearing the cache or running the cookbook on a fresh server? |
Right, By overiding the pip_version in attribute file of wrapper cookbook resolving the issue now.
thanks for the help. |
The setup_python recipe doesn't work with the latest version of pip 18.1 https://pypi.org/project/pip/18.1/#history Issue is open at poise/poise-python#133 The workaround consists in overriding pip version to 18.0 Signed-off-by: Luca Carrogu <carrogu@amazon.com>
The setup_python recipe doesn't work with the latest version of pip 18.1 https://pypi.org/project/pip/18.1/#history Issue is open at poise/poise-python#133 The workaround consists in overriding pip version to 18.0 Signed-off-by: Luca Carrogu <carrogu@amazon.com>
The setup_python recipe doesn't work with the latest version of pip 18.1 https://pypi.org/project/pip/18.1/#history Issue is open at poise/poise-python#133 The workaround consists in overriding pip version to 18.0 Signed-off-by: Luca Carrogu <carrogu@amazon.com>
Just a note to some folks for whom the workarounds above might show no effect: If pip==18.1 is already installed (and your resource is using the provider: system option), the broken script is executed with that version and fails before pip can be downgraded. So in that case you may need to run Let's hope the patch in #134 gets merged soon. A long-term solution that does not depend on any pip internals would be even nicer. |
There is a bug in the poise-python cookbook because it depends on internal features of pip and these internals have changed in pip 18.1, see [0]. We have a workaround in the openstack-common cookbook proposed, but that doesn't work if the server has pip 18.1 pre-installed, as seems to be the case for the infra-provided CI image. So as a further workaround we need to downgrade the pre-installed pip version for the time being. [0] poise/poise-python#133 Depends-On: https://review.openstack.org/610427 Change-Id: I52514691d3f271579628b62539222f7307957ba0
There is a bug in the poise-python cookbook because it depends on internal features of pip and these internals have changed in pip 18.1, see [0]. We have a workaround in the openstack-common cookbook proposed, but that doesn't work if the server has pip 18.1 pre-installed, as seems to be the case for the infra-provided CI image. So as a further workaround we need to downgrade the pre-installed pip version for the time being. [0] poise/poise-python#133 Depends-On: https://review.openstack.org/610427 Change-Id: I52514691d3f271579628b62539222f7307957ba0 (cherry picked from commit 973119b)
There is a bug in the poise-python cookbook because it depends on internal features of pip and these internals have changed in pip 18.1, see [0]. We have a workaround in the openstack-common cookbook proposed, but that doesn't work if the server has pip 18.1 pre-installed, as seems to be the case for the infra-provided CI image. So as a further workaround we need to downgrade the pre-installed pip version for the time being. [0] poise/poise-python#133 Depends-On: https://review.openstack.org/610427 Change-Id: I52514691d3f271579628b62539222f7307957ba0 (cherry picked from commit 973119b)
As a workaround, since we need this to work to deploy our software using
Then when 1.7.1 is really released, I will switch back to using the version from the Chef Supermarket. Posting this here in case others might find it helpful. You're welcome to use this or fork it and use it from your own repo. |
when is the 1.7.1 version getting released? |
Why is 1.7.1 not out yet? :( |
I explained this on another issue, but my CI system is pretty much busted so I have no safe way to vet a release. No one seems to be willing to pay for the time it would take to fix and I’m no longer doing pro-bono Chef work when I can avoid it. |
@coderanger How could we collaborate to help...? At Twistle we're using this code as part of our chef build for a production project, so maybe there's a way to help. It seems like others are in similar positions. Would you be willing to point me at the other issue where you explained the problem? |
@coderanger P.S. I get not wanting to do volunteer work using chef. I feel the same way! 🙂 |
I’m on my phone so easier to just summarize here again: the first issue is that since my last release, Travis CI has cut the maximum time for builds from two hours to one, which means my tests get killed. But I’m not inclined to fix that because the second issue is my (very generous) infrastructure sponsor will sadly be terminating their open source sponsorship program so the infra that my tests actually run on will go away in a few more weeks. So to get my CI back into a healthy state would require a pretty major rebuild, probably switching providers as well as reworking things to not use the dedicated infra (which will make the tests even slower). |
@coderanger I might be able to help with this via the OSUOSL. PM me on slack if you're interested. |
@ramereth Cool! @coderanger I might be able to help with moving things over to a new provider if you need more help. Maybe there are others that could pitch in too? |
Also note, until poise/poise-python@861bf06 is released, you once have to manually `apt install python3.6-distutils python3.6-venv`
This branch and fork to be removed when poise-python is released. poise#133 (comment)
I don't understand, it worked in the past.
The text was updated successfully, but these errors were encountered: