Skip to content

Fix incorrect scp exit status for OpenSSH nodes#58288

Merged
atburke merged 1 commit intomasterfrom
atburke/sftp-fwd-status
Aug 25, 2025
Merged

Fix incorrect scp exit status for OpenSSH nodes#58288
atburke merged 1 commit intomasterfrom
atburke/sftp-fwd-status

Conversation

@atburke
Copy link
Copy Markdown
Contributor

@atburke atburke commented Aug 22, 2025

This change fixes a bug where an scp with both OpenSSH client and server would have an exit status of 1, regardless of whether or not the transfer succeeded.

Fixes #20863.

Changelog: Fixed incorrect scp exit status between OpenSSH clients and servers

@public-teleport-github-review-bot public-teleport-github-review-bot bot removed the request for review from aadc-dev August 25, 2025 18:44
@atburke atburke added this pull request to the merge queue Aug 25, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 25, 2025
@atburke atburke added this pull request to the merge queue Aug 25, 2025
Merged via the queue into master with commit 2b4870e Aug 25, 2025
45 checks passed
@atburke atburke deleted the atburke/sftp-fwd-status branch August 25, 2025 20:03
@backport-bot-workflows
Copy link
Copy Markdown
Contributor

@atburke See the table below for backport results.

Branch Result
branch/v16 Failed
branch/v17 Create PR
branch/v18 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

scp returning non-zero exit code on successful transfer

3 participants