-
Notifications
You must be signed in to change notification settings - Fork 138
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
Web-UI update fails to recreate venv #2652 #2654
Web-UI update fails to recreate venv #2652 #2654
Conversation
Unset no longer required, and counterproductive to Poetry venv rebuild, VIRTUAL_ENV environmental variable within the programmatically created AT update script.
Thanks a lot for taking the time to find the fix create the issue, and prepare the PR! If I'm correct, this fix will apply only to future updates after the one containing this PR, but I don't see any other way so far. We always have the functioning update through cli so far. |
@FroggyFlox Re:
Yes, but we have only seen this failure (without by-hand recreation) on our as-yet unsupported 15.5 base OS. So getting this out before we begin that support was the hope. Plus we only cover 15.5 in testing (officially) as of yet. Thanks for the clarification on this one. Quite important point as it goes. I've now successfully built and installed a 15.5 hosted rpm with this patch pre-applied, and given we have tested this fix in development re it's modified update script fixing the observed issue, I'll go ahead and get this merged. |
Testing:An rpm with these modification in place as version 5.0.2-2654 successfully updated via Web-UI to 5.0.2-2655 (built to test a later unrelated pull request).
and root's notification email detailing this update:
N.B. contextual information re our outstanding issue #2651 & rockstor/rockstor-rpmbuild#43 where we currently fail to restart our services:
|
Unset no longer required, and counterproductive to Poetry venv rebuild, VIRTUAL_ENV environmental variable within the programmatically created AT update script.
Fixes #2652
See issue text for development context.