-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
"Exception: Failed to create virtualenv" during packs.install #53
Comments
probably related: #50 |
@dennybaa this one has higher priority, since it's blocker for puppet installer (where many st2 packages are installed). |
Python bin directory location should NOT rely on PATH, it should use same mechanism which is used to locate python binary and fallback to PATH (optionally). |
Just FYI there is By default, that is the |
Fix for this issue is discussed here: StackStorm/st2#2339 |
I was able to work around this for actions by adding This allowed me to get the virtualenv created and to successfully run actions. The problem as it stands now is that sensors do not work. Since the virtualenv for the pack was created using the st2actions venv and not the st2reactor venv. There were a couple other hacks to the packs pack necessary but that isn't relevant to this issue. I'll open a separate PR on those. |
@DoriftoShoes nice, but we should not rely upon this work around... It's better What comes to my mind, that we should get st2actionrunner (probably even st2 binary, i.e. python with which process is invoked) interpreter path, and evaluate virtualenv path accordingly. What do you think gentlemen? |
@dennybaa @Kami: I was playing around with virtualenv paths and it doesn't make a difference. See gist here: https://gist.github.com/lakshmi-kannan/bddd20683f5fe4a49013 Patrick's --always-copy fixes the issue irrespective of which virtualenv binary is used. I will validate if this option works with existing packages. |
Confirmed with without with |
@lakshmi-kannan , @here. Awesome, and thank you! I confirm that without copying ( First important: why virtualenv doesn't work without
So just look, it's possible to run
After this Okay summing it up, it's possible to reduce virtualenv size to minimum (almost to 0) via hard linking. But another important thing arises (upgrade story??), what is post upgrade st2 and pack story!? Using |
fixing last portion #76
el7:
|
i think closing. since already merged and tested using CircleCI... |
Reproduce (Ubuntu14)
Error message
Helpful Info:
Broken symlinks:
https://github.com/StackStorm/st2/blob/master/contrib/packs/actions/pack_mgmt/setup_virtualenv.py might have answers.
The text was updated successfully, but these errors were encountered: