-
Notifications
You must be signed in to change notification settings - Fork 93
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
remote tasks load wrong passphrase if suite name is registered remotely too #1763
Comments
I guess we need to change the logic to favour the passphrase file installed under |
matthewrmshin
added a commit
to matthewrmshin/cylc-flow
that referenced
this issue
Apr 5, 2016
New test to ensure that passphrase search on remote job host is correct even if there is a non-running registered suite on the remote job with the same name. See cylc#1763.
matthewrmshin
added a commit
to matthewrmshin/cylc-flow
that referenced
this issue
Apr 8, 2016
New test to ensure that passphrase search on remote job host is correct even if there is a non-running registered suite on the remote job with the same name. See cylc#1763.
matthewrmshin
added a commit
to matthewrmshin/cylc-flow
that referenced
this issue
Apr 14, 2016
New test to ensure that passphrase search on remote job host is correct even if there is a non-running registered suite on the remote job with the same name. See cylc#1763.
matthewrmshin
added a commit
to matthewrmshin/cylc-flow
that referenced
this issue
Apr 15, 2016
New test to ensure that passphrase search on remote job host is correct even if there is a non-running registered suite on the remote job with the same name. See cylc#1763.
matthewrmshin
added a commit
to matthewrmshin/cylc-flow
that referenced
this issue
Apr 20, 2016
New test to ensure that passphrase search on remote job host is correct even if there is a non-running registered suite on the remote job with the same name. See cylc#1763.
matthewrmshin
added a commit
to matthewrmshin/cylc-flow
that referenced
this issue
Apr 21, 2016
New test to ensure that passphrase search on remote job host is correct even if there is a non-running registered suite on the remote job with the same name. See cylc#1763.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I run a suite called SUITE on SUITE_HOST that submits a task to TASK_HOST, the remote task can load the wrong passphrase if TASK_HOST also has a suite registered as SUITE (with a passphrase in its suite definition directory).
The text was updated successfully, but these errors were encountered: