-
Notifications
You must be signed in to change notification settings - Fork 900
Disable the LSF plm if CSM is detected #4439
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
Conversation
LSF running on top of CSM does not provide LSF daemons on the compute nodes. Signed-off-by: Matt Ezell <[email protected]>
Can one of the admins verify this patch? |
ok to test |
Sorry this got lost in the run up to SC. I'll try to get to it early this week. Sorry for the delay. |
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.
This is good. Thanks!
There are some environments/setups where the CSM_ALLOCATION_ID
might be set, but LSF can still be used to launch. However, there is no good way of detecting that scenario at the moment. We will work on a way to better detect that in a future PR.
@mattaezell Do you want this change in the three release branches ( |
Thanks @jjhursey. I'm not sure exactly what versions people are testing with here locally, let me check. |
@mattaezell I filed PRs to take this to the v3.0.x and v3.1.x series. Sorry for the delay. |
LSF running on top of CSM does not provide LSF daemons on the compute nodes. Attempts to run will result in errors like: