-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu 16.04 failure to provision using enova-python. #4
Comments
I can reproduce the issue with the local kitchen tests using The relevant message from the log is at:
which is the same error message that I get when trying to use the cookbook. |
I applied the patch located at shareaholic/poise-python@929195a and it seems to have made the job succeed. |
Hi @thomasdziedzic-pd thanks for reporting the issue. If you have time to submit a PR that would be amazing, otherwise I can work on integrating your changes to this cookbook sometime next week. Also, you might want to remove your public IP from the logs in the description if you care about such things. |
I'm trying to figure out some permissions issue with forking cookbooks, if I manage to figure it out I will try and submit one!
The machine was already decommissioned by the time I posted the logs. |
As a follow up to:
I wasn't able to resolve this so I wont be submitting a PR unfortunately. |
@thomasdziedzic-pd super sorry for the delay on this. I'll follow up by end of month. My apologies. |
Here is my first round fix for this: I overlayed ndpgroup/poise-python changes over your generated cookbook in addition to fixing this bug, but the hack script changes in that should be able to be grabbed without also pulling in the other changes. |
I pushed another fix for the hack script as 1.8.12 on our fork. I have manually tested this version of the hack script against all pip versions from 8.1.1 to 20.3.3 using Python 2.7 to address a few more bugs on pip 19.3.x and higher. |
I have the following lines in my recipe to try to install python2:
When I tried to provision a new host, I got the following error message:
This might be related to #3 (comment) since they had an error in the CI during setuptools install as well.
Thanks for your time!
The text was updated successfully, but these errors were encountered: