Skip to content

SSH command silently fails #22

@MarkBennett

Description

@MarkBennett

I had an EC2 instance which was re-using and old IP. When this happened SSH wouldn't connect as the key in known_hosts had changed. SSHing in to the box manually generated an error, but plow would run with no output at all. Removing the key caused plow to operate normally.

We need to make plow handle SSH errors with an error message that will indicate what's wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions