Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Node str/toDict do not check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists #297

Open
nbastin opened this issue Mar 19, 2024 · 0 comments
Open

Node str/toDict do not check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists #297

nbastin opened this issue Mar 19, 2024 · 0 comments
Assignees
@sajith

Comments

@nbastin
Copy link

nbastin commented Mar 19, 2024

When you submit your slice (or otherwise print the node table for your slice), there's a column for "SSH Command" which will happily tell you to use an ssh config file (via -F) which does not exist.
@nbastin nbastin changed the title Node str doesn't check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists Node __str__/toDict don;t't check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists Mar 19, 2024
@nbastin nbastin changed the title Node __str__/toDict don;t't check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists Node __str__/toDict do not check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists Mar 19, 2024
@nbastin nbastin changed the title Node __str__/toDict do not check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists Node str/toDict do not check if DEFAULT_FABRIC_BASTION_SSH_CONFIG_FILE actually exists Mar 19, 2024
@sajith sajith self-assigned this Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sajith sajith

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sajith @nbastin