Fix interactive tools on the secondary HTCondor cluster #1006
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make the environment variables available to the Galaxy handlers also available to the systemd-nspawn HTCondor container (submit role). This fixes interactive tools on the secondary HTCondor cluster. They were not working because the IT monitoring script was running on system's Python instead of on the virtualenv's Python.
bgruening
approved these changes
Nov 22, 2023
Place the file containing the environment variables needed for condor_submit to work properly in the home directory of the Galaxy user, set its owner to the Galaxy user.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make the environment variables available to the Galaxy handlers also available to the systemd-nspawn HTCondor container (submit role).
This fixes interactive tools on the secondary HTCondor cluster. They were not working because the IT monitoring script was running on system's Python instead of on the virtualenv's Python.