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

Dump SSH debug level logs if initial connection to guest fails #4855

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

roypat
Copy link
Contributor

@roypat roypat commented Oct 16, 2024

When doing _init_connection, set SSHs debug level to most verbose, so
that in case a connection failure occurs, we can look at the SSH logs
(both local and remote, see man ssh(1)).

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • If a specific issue led to this PR, this PR closes the issue.
  • The description of changes is clear and encompassing.
  • Any required documentation changes (code and docs) are included in this
    PR.
  • API changes follow the Runbook for Firecracker API changes.
  • User-facing changes are mentioned in CHANGELOG.md.
  • All added/changed functionality is tested.
  • New TODOs link to an issue.
  • Commits meet
    contribution quality standards.

  • This functionality cannot be added in rust-vmm.

When doing `_init_connection`, set SSHs debug level to most verbose, so
that in case a connection failure occurs, we can look at the SSH logs
(both local and remote, see man ssh(1)).

Usually, SSH debug logs would clobber with output from the actual
command being run over the SSH connection, however since we're just
running `true`, and are not trying to do anything with its output,
that's fine in this case.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
it was referring to a `no_shell` parameter, instead of the `shell`
parameter.

Fixes: cb61379
Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Copy link

codecov bot commented Oct 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.05%. Comparing base (a31c79a) to head (108a941).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4855   +/-   ##
=======================================
  Coverage   84.05%   84.05%           
=======================================
  Files         251      251           
  Lines       28061    28061           
=======================================
  Hits        23588    23588           
  Misses       4473     4473           
Flag Coverage Δ
5.10-c5n.metal 84.68% <ø> (+<0.01%) ⬆️
5.10-m5n.metal 84.66% <ø> (ø)
5.10-m6a.metal 83.97% <ø> (ø)
5.10-m6g.metal 80.67% <ø> (ø)
5.10-m6i.metal 84.66% <ø> (ø)
5.10-m7g.metal 80.67% <ø> (ø)
6.1-c5n.metal 84.67% <ø> (-0.01%) ⬇️
6.1-m5n.metal 84.66% <ø> (ø)
6.1-m6a.metal 83.97% <ø> (ø)
6.1-m6g.metal 80.67% <ø> (+<0.01%) ⬆️
6.1-m6i.metal 84.66% <ø> (ø)
6.1-m7g.metal 80.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@roypat roypat added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Oct 16, 2024
@roypat roypat merged commit 4b79156 into firecracker-microvm:main Oct 16, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Awaiting review Indicates that a pull request is ready to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants