-
Notifications
You must be signed in to change notification settings - Fork 46
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
Adding support for glidein to use cvmfsexec in mode 3 when possible #245
Conversation
da8b3f0
to
9fa694e
Compare
4366607
to
9fa694e
Compare
Reopening this in draft mode until the changes are ready for review. |
e5e08c5
to
9734fbf
Compare
- removed print statements used primarily for debugging the code - updated indentation in the code files to remain consistent with other scripts - updated mentions and references for mode 2 with mode 1 to stay consistent with cvmfsexec documentation
- removed the previously existing version of cvmfs setup script since a new version is in place - updated the node validation script based on linting suggestions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requesting some changes.
: | ||
if [[ $glidein_cvmfs = required ]]; then | ||
# if mount CVMFS is not successful, report an error and exit with failure exit code | ||
echo $? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exit code to stdout before exit? Will always be 0
elif [[ $glidein_cvmfs = preferred || $glidein_cvmfs = optional ]]; then | ||
# if mount CVMFS is not successful, report a warning/error in the logs and continue with glidein startup | ||
# script status must be OK, otherwise the glidein will fail | ||
echo $? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exit code to stdout? Will always be 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove echo $? will always return a zero because of the previous if condition always evaluating to zero
if wanting to print to stdout, then use echo 0/1
if wanting to capture the exit code of the previous command, this does not capture it. I would have to put that into a variable first and then use
Closing this pull request without merging as a new PR (#372) has superseded this. |
This PR contains changes (additions/modifications) towards enabling the glidein to support the use of cvmfsexec in mode 3 when possible. While this PR primarily encompasses changes pertaining to enabling mode 3 support, it also contains a change to the existing logic for script duplication check.
TODO: Make sure that cvmfsexec is used only if there is a working squid proxy