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.

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

ssh failure conditions never propagate to callers #298

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

ssh failure conditions never propagate to callers #298

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

Comments

@nbastin
Copy link

nbastin commented Mar 19, 2024

In cases where your sliver is messed up (which seems to happen a lot), fablib silently ignores all ssh failure conditions and never tells the user about them (other than returning None from Node/Interface methods).

For example this happens when I try to ssh directly to a broken node in a slice (other nodes work fine):

$ ssh -F ~/.ssh/fabric_ssh_config ubuntu@2001:18e8:fff0:3:f816:3eff:fe8a:4074
channel 0: open failed: connect failed: No route to host
stdio forwarding failed
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535

but this never propagates to a caller of a fablib method, so I can't tell the difference between something that hasn't yet been configured and a node that is unreachable.

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants