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

Cloud: Check the exit status code of scp before assuming it has failed. #16599

Merged

Conversation

akatrevorjay
Copy link

Latest 2014.1 broke salt-cloud due to this. With this small patch I can deploy instances again.

@ghost
Copy link

ghost commented Oct 13, 2014

Test Failed.

If the failures are unrelated to your code, don't stress, a core developer will know these apart.
In the future, if possible, please branch off a passing commit to avoid false positives.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/9103/

thatch45 added a commit that referenced this pull request Oct 13, 2014
…-code

Cloud: Check the exit status code of scp before assuming it has failed.
@thatch45 thatch45 merged commit 25cf706 into saltstack:2014.1 Oct 13, 2014
@thatch45 thatch45 added the bugfix-bckport will be be back-ported to an older release branch by creating a PR against that branch label Oct 13, 2014
@awestendorf
Copy link

Can you please release a package with this fix in it ASAP? salt-cloud is currently broken, and trying to use the fix in #16437 doesn't work because even with use_sftp: False, sftp is used and then fails.

@cachedout
Copy link
Contributor

HI Aaron. We had passing tests on 2014.1.12. Is that the version that
you're seeing salt-cloud failures on?

On Tue, Oct 14, 2014 at 8:59 AM, Aaron Westendorf notifications@github.com
wrote:

Can you please release a package with this fix in it ASAP? salt-cloud is
currently broken, and trying to use the fix in #16437
#16437 doesn't work because
even with use_sftp: False, sftp is used and then fails.


Reply to this email directly or view it on GitHub
#16599 (comment).

@rallytime rallytime removed the bugfix-bckport will be be back-ported to an older release branch by creating a PR against that branch label Oct 14, 2014
@akatrevorjay
Copy link
Author

@cachedout I saw this problem in 2014.1.12 as well.

@cachedout
Copy link
Contributor

@akaihola OK. Thanks for letting us know.

@techhat
Copy link
Contributor

techhat commented Oct 15, 2014

Got stung by this today too. Moving back to 2014.1.10 took care of me.

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

Successfully merging this pull request may close these issues.

None yet

6 participants