Any plan for CHEF-2627 (Knife SSH should return exit code based on whether or not ssh command is successful or not)


#1

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket
http://tickets.opscode.com/browse/CHEF-2627
( http://tickets.opscode.com/browse/CHEF-2627Knife SSH should return exit
code based on whether or not ssh command is successful or
nothttp://tickets.opscode.com/browse/CHEF-2627)
? I really want to know whether the command Chef::knife::Bootstrap.run
(which calls Chef::knife::Ssh.run) is successful or not, so I can perform
next step based on the result.

Thanks & Best Regards,
Hui Hu


#2

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel. Diagnostic output is hard to miss when there are many machines. Knife should at the very least exit a non-zero status, and optimally print at the end of the session list of machines with non-zero exit status (and the respective statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit code based on whether or not ssh command is successful or not) ? I really want to know whether the command Chef::knife::Bootstrap.run (which calls Chef::knife::Ssh.run) is successful or not, so I can perform next step based on the result.

Thanks & Best Regards,
Hui Hu


#3

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel. Diagnostic output is hard to miss when there are many machines. Knife should at the very least exit a non-zero status, and optimally print at the end of the session list of machines with non-zero exit status (and the respective statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit code based on whether or not ssh command is successful or not) ? I really want to know whether the command Chef::knife::Bootstrap.run (which calls Chef::knife::Ssh.run) is successful or not, so I can perform next step based on the result.

Thanks & Best Regards,
Hui Hu


#4

I don’t see how this is a useless feature. Without writing any additional code to scrub the output of Knife SSH or reading it yourself, how do you know if 1 out of the 400 nodes you just sent a command to failed?

Command line tools should return with a status code which communicates to the user if their intentions were successful or not, and if possible, why (this is why we don’t just have two exit codes - 0 or 1). As it is, Knife SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute their commands successfully sounds like a very fair request and how I would expect Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done. You should sign the CLA and do the work if you want this ticket expedited.


Jamie Winsor
@resetexistence

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki <maciej@pasternacki.net (mailto:maciej@pasternacki.net)> wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel. Diagnostic output is hard to miss when there are many machines. Knife should at the very least exit a non-zero status, and optimally print at the end of the session list of machines with non-zero exit status (and the respective statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit code based on whether or not ssh command is successful or not) ? I really want to know whether the command Chef::knife::Bootstrap.run (which calls Chef::knife::Ssh.run) is successful or not, so I can perform next step based on the result.

Thanks & Best Regards,
Hui Hu


#5

This won’t solve your knife issues, but I bet you’d enjoy a look into chef’s exception and report handlers: http://wiki.opscode.com/display/chef/Exception+and+Report+Handlers

I’m especially fond of:

  • chef-handler-updated-resources
  • airbrake_handler
  • chef-syslog-handler

On 2012-05-02, at 08:17, Maciej Pasternacki wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel. Diagnostic output is hard to miss when there are many machines. Knife should at the very least exit a non-zero status, and optimally print at the end of the session list of machines with non-zero exit status (and the respective statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit code based on whether or not ssh command is successful or not) ? I really want to know whether the command Chef::knife::Bootstrap.run (which calls Chef::knife::Ssh.run) is successful or not, so I can perform next step based on the result.

Thanks & Best Regards,
Hui Hu


#6

Thanks Jamie and Maciej for your further explanation on this feature
request.

I’ve figured out a patch which works in my case. Will try to send a pull
request for Chef devs to review.

Thanks & Best Regards,
Hui Hu

2012/5/3 Jamie Winsor jamie@vialstudios.com

I don’t see how this is a useless feature. Without writing any additional
code to scrub the output of Knife SSH or reading it yourself, how do you
know if 1 out of the 400 nodes you just sent a command to failed?

Command line tools should return with a status code which communicates to
the user if their intentions were successful or not, and if possible, why
(this is why we don’t just have two exit codes - 0 or 1). As it is, Knife
SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute their
commands successfully sounds like a very fair request and how I would
expect Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done. You
should sign the CLA and do the work if you want this ticket expedited.


Jamie Winsor
@resetexistence
https://github.com/reset

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel.
Diagnostic output is hard to miss when there are many machines. Knife
should at the very least exit a non-zero status, and optimally print at the
end of the session list of machines with non-zero exit status (and the
respective statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket
http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit
code based on whether or not ssh command is successful or not) ? I really
want to know whether the command Chef::knife::Bootstrap.run (which calls
Chef::knife::Ssh.run) is successful or not, so I can perform next step
based on the result.

Thanks & Best Regards,
Hui Hu


#7

This feature (or, more precisely, fixing this bug where knife does not follow UNIX conventions) is as useful as ‘knife ssh’ command itself is.

If knife ssh command is useful in its own right, it is just a “search in chef server” layer over plain command-line SSH. My expectation then is that it behaves like ssh command, especially with regard to being used in scripts. SSH does relay remote command’s exit status even though ssh connection itself has been successful and the command has been called correctly:

ssh ronja.3ofcoins.net false ; echo ?
1

As a consequence, this is behaviour I’d expect from any convenience layer over SSH.

Now if knife ssh is useless on its own and exists only for knife bootstrap and knife * server create (because using it as its own command is going into “SSH-as-a-framework” territory), then I’d also expect it to return failure when node bootstrap script failed on the remote site - non-zero exit status from bootstrap script is a failure.

Suggestion to contribute the patch is justified. I’m going to EOT here and start coding - this will be more productive.

– Maciej

On May 2, 2012, at 21:32 , Jamie Winsor wrote:

I don’t see how this is a useless feature. Without writing any additional code to scrub the output of Knife SSH or reading it yourself, how do you know if 1 out of the 400 nodes you just sent a command to failed?

Command line tools should return with a status code which communicates to the user if their intentions were successful or not, and if possible, why (this is why we don’t just have two exit codes - 0 or 1). As it is, Knife SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute their commands successfully sounds like a very fair request and how I would expect Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done. You should sign the CLA and do the work if you want this ticket expedited.


Jamie Winsor
@resetexistence
https://github.com/reset

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel. Diagnostic output is hard to miss when there are many machines. Knife should at the very least exit a non-zero status, and optimally print at the end of the session list of machines with non-zero exit status (and the respective statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit code based on whether or not ssh command is successful or not) ? I really want to know whether the command Chef::knife::Bootstrap.run (which calls Chef::knife::Ssh.run) is successful or not, so I can perform next step based on the result.

Thanks & Best Regards,
Hui Hu


#8

Hello Chef,

I’ve send out a pull request ( https://github.com/opscode/chef/pull/285 )
to fix http://tickets.opscode.com/browse/CHEF-2627 . Please review it and
have a try on your env :slight_smile:

Thanks & Best Regards,
Hui Hu

2012/5/3 Hui Hu huhui14@gmail.com

Thanks Jamie and Maciej for your further explanation on this feature
request.

I’ve figured out a patch which works in my case. Will try to send a pull
request for Chef devs to review.

Thanks & Best Regards,
Hui Hu

2012/5/3 Jamie Winsor jamie@vialstudios.com

I don’t see how this is a useless feature. Without writing any
additional code to scrub the output of Knife SSH or reading it yourself,
how do you know if 1 out of the 400 nodes you just sent a command to
failed?

Command line tools should return with a status code which communicates to
the user if their intentions were successful or not, and if possible, why
(this is why we don’t just have two exit codes - 0 or 1). As it is, Knife
SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute their
commands successfully sounds like a very fair request and how I would
expect Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done. You
should sign the CLA and do the work if you want this ticket expedited.


Jamie Winsor
@resetexistence
https://github.com/reset

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel.
Diagnostic output is hard to miss when there are many machines. Knife
should at the very least exit a non-zero status, and optimally print at the
end of the session list of machines with non-zero exit status (and the
respective statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket
http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return
exit code based on whether or not ssh command is successful or not) ? I
really want to know whether the command Chef::knife::Bootstrap.run (which
calls Chef::knife::Ssh.run) is successful or not, so I can perform next
step based on the result.

Thanks & Best Regards,
Hui Hu


#9

Great work Hui Hu.

Apologies for my original tone. I didn’t mean to offend – although,
if you were offended; perhaps you should re-evaluate your options.

–AJ

On 5 May 2012 04:50, Hui Hu huhui14@gmail.com wrote:

Hello Chef,

I’ve send out a pull request ( https://github.com/opscode/chef/pull/285 )
to fix http://tickets.opscode.com/browse/CHEF-2627 . Please review it and
have a try on your env :slight_smile:

Thanks & Best Regards,
Hui Hu

2012/5/3 Hui Hu huhui14@gmail.com

Thanks Jamie and Maciej for your further explanation on this feature
request.

I’ve figured out a patch which works in my case. Will try to send a pull
request for Chef devs to review.

Thanks & Best Regards,
Hui Hu

2012/5/3 Jamie Winsor jamie@vialstudios.com

I don’t see how this is a useless feature. Without writing any additional
code to scrub the output of Knife SSH or reading it yourself, how do you
know if 1 out of the 400 nodes you just sent a command to failed?

Command line tools should return with a status code which communicates to
the user if their intentions were successful or not, and if possible, why
(this is why we don’t just have two exit codes - 0 or 1). As it is, Knife
SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute their
commands successfully sounds like a very fair request and how I would expect
Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done. You
should sign the CLA and do the work if you want this ticket expedited.


Jamie Winsor
@resetexistence
https://github.com/reset

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel.
Diagnostic output is hard to miss when there are many machines. Knife should
at the very least exit a non-zero status, and optimally print at the end of
the session list of machines with non-zero exit status (and the respective
statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket
http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit
code based on whether or not ssh command is successful or not) ? I really
want to know whether the command Chef::knife::Bootstrap.run (which calls
Chef::knife::Ssh.run) is successful or not, so I can perform next step based
on the result.

Thanks & Best Regards,
Hui Hu


#10

Please do not feed trolls. Hugs and patches only.

On 2012-05-04, at 22:14, AJ Christensen wrote:

Great work Hui Hu.

Apologies for my original tone. I didn’t mean to offend – although,
if you were offended; perhaps you should re-evaluate your options.

–AJ

On 5 May 2012 04:50, Hui Hu huhui14@gmail.com wrote:

Hello Chef,

I’ve send out a pull request ( https://github.com/opscode/chef/pull/285 )
to fix http://tickets.opscode.com/browse/CHEF-2627 . Please review it and
have a try on your env :slight_smile:

Thanks & Best Regards,
Hui Hu

2012/5/3 Hui Hu huhui14@gmail.com

Thanks Jamie and Maciej for your further explanation on this feature
request.

I’ve figured out a patch which works in my case. Will try to send a pull
request for Chef devs to review.

Thanks & Best Regards,
Hui Hu

2012/5/3 Jamie Winsor jamie@vialstudios.com

I don’t see how this is a useless feature. Without writing any additional
code to scrub the output of Knife SSH or reading it yourself, how do you
know if 1 out of the 400 nodes you just sent a command to failed?

Command line tools should return with a status code which communicates to
the user if their intentions were successful or not, and if possible, why
(this is why we don’t just have two exit codes - 0 or 1). As it is, Knife
SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute their
commands successfully sounds like a very fair request and how I would expect
Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done. You
should sign the CLA and do the work if you want this ticket expedited.


Jamie Winsor
@resetexistence
https://github.com/reset

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel.
Diagnostic output is hard to miss when there are many machines. Knife should
at the very least exit a non-zero status, and optimally print at the end of
the session list of machines with non-zero exit status (and the respective
statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket
http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit
code based on whether or not ssh command is successful or not) ? I really
want to know whether the command Chef::knife::Bootstrap.run (which calls
Chef::knife::Ssh.run) is successful or not, so I can perform next step based
on the result.

Thanks & Best Regards,
Hui Hu


#11

Hui Hu: Take a look at the how to contribute page that AJ linked to
before, you will need to update the ticket with information for
pulling in your changes and mark the ticket resolved (if this resolves
it) for it to be reviewed for inclusion in the next release.

-Jesse

On Fri, May 4, 2012 at 6:21 PM, Joseph Holsten joseph@josephholsten.com wrote:

Please do not feed trolls. Hugs and patches only.

On 2012-05-04, at 22:14, AJ Christensen wrote:

Great work Hui Hu.

Apologies for my original tone. I didn’t mean to offend – although,
if you were offended; perhaps you should re-evaluate your options.

–AJ

On 5 May 2012 04:50, Hui Hu huhui14@gmail.com wrote:

Hello Chef,

I’ve send out a pull request ( https://github.com/opscode/chef/pull/285 )
to fix http://tickets.opscode.com/browse/CHEF-2627 . Please review it and
have a try on your env :slight_smile:

Thanks & Best Regards,
Hui Hu

2012/5/3 Hui Hu huhui14@gmail.com

Thanks Jamie and Maciej for your further explanation on this feature
request.

I’ve figured out a patch which works in my case. Will try to send a pull
request for Chef devs to review.

Thanks & Best Regards,
Hui Hu

2012/5/3 Jamie Winsor jamie@vialstudios.com

I don’t see how this is a useless feature. Without writing any additional
code to scrub the output of Knife SSH or reading it yourself, how do you
know if 1 out of the 400 nodes you just sent a command to failed?

Command line tools should return with a status code which communicates to
the user if their intentions were successful or not, and if possible, why
(this is why we don’t just have two exit codes - 0 or 1). As it is, Knife
SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute their
commands successfully sounds like a very fair request and how I would expect
Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done. You
should sign the CLA and do the work if you want this ticket expedited.


Jamie Winsor
@resetexistence
https://github.com/reset

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute it
yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel.
Diagnostic output is hard to miss when there are many machines. Knife should
at the very least exit a non-zero status, and optimally print at the end of
the session list of machines with non-zero exit status (and the respective
statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket
http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should return exit
code based on whether or not ssh command is successful or not) ? I really
want to know whether the command Chef::knife::Bootstrap.run (which calls
Chef::knife::Ssh.run) is successful or not, so I can perform next step based
on the result.

Thanks & Best Regards,
Hui Hu


#12

Hi Jesse, All,

Thanks for your hints. I’ve mark the ticket
http://tickets.opscode.com/browse/CHEF-2627 as ‘Resolved’, the patch is
attached on ticket. Please help review and have a try on your env :slight_smile:

Thanks & Best Regards,
Hui Hu, Beijing, China

2012/5/5 Jesse Campbell hikeit@gmail.com

Hui Hu: Take a look at the how to contribute page that AJ linked to
before, you will need to update the ticket with information for
pulling in your changes and mark the ticket resolved (if this resolves
it) for it to be reviewed for inclusion in the next release.

-Jesse

On Fri, May 4, 2012 at 6:21 PM, Joseph Holsten joseph@josephholsten.com
wrote:

Please do not feed trolls. Hugs and patches only.

On 2012-05-04, at 22:14, AJ Christensen wrote:

Great work Hui Hu.

Apologies for my original tone. I didn’t mean to offend – although,
if you were offended; perhaps you should re-evaluate your options.

–AJ

On 5 May 2012 04:50, Hui Hu huhui14@gmail.com wrote:

Hello Chef,

I’ve send out a pull request (
https://github.com/opscode/chef/pull/285 )

to fix http://tickets.opscode.com/browse/CHEF-2627 . Please review
it and

have a try on your env :slight_smile:

Thanks & Best Regards,
Hui Hu

2012/5/3 Hui Hu huhui14@gmail.com

Thanks Jamie and Maciej for your further explanation on this feature
request.

I’ve figured out a patch which works in my case. Will try to send a
pull

request for Chef devs to review.

Thanks & Best Regards,
Hui Hu

2012/5/3 Jamie Winsor jamie@vialstudios.com

I don’t see how this is a useless feature. Without writing any
additional

code to scrub the output of Knife SSH or reading it yourself, how do
you

know if 1 out of the 400 nodes you just sent a command to failed?

Command line tools should return with a status code which
communicates to

the user if their intentions were successful or not, and if
possible, why

(this is why we don’t just have two exit codes - 0 or 1). As it is,
Knife

SSH fails silently when commanding multiple nodes.

A non zero exit code with an output of nodes that did not execute
their

commands successfully sounds like a very fair request and how I
would expect

Knife SSH to behave.

Hui Hu - it shouldn’t be a terribly difficult task to get this done.
You

should sign the CLA and do the work if you want this ticket
expedited.


Jamie Winsor
@resetexistence
https://github.com/reset

On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:

The feature sounds so incredibly useless you may have to contribute
it

yourself. Even then I’d be dubious about it being accepted apart from
solely as a bug fix.

You do not need an SSH-as-a-framework system.

http://wiki.opscode.com/display/chef/How+to+Contribute

–AJ

On 2 May 2012 20:17, Maciej Pasternacki maciej@pasternacki.net
wrote:

BIG +1 on this.

I’m using knife ssh to execute maintenance commands in parallel.
Diagnostic output is hard to miss when there are many machines.
Knife should

at the very least exit a non-zero status, and optimally print at the
end of

the session list of machines with non-zero exit status (and the
respective

statuses).

– M

On May 2, 2012, at 7:53 , Hui Hu wrote:

Hello,

I’ve been using Chef for several months.

Are Chef developers going to fix this ticket
http://tickets.opscode.com/browse/CHEF-2627 (Knife SSH should
return exit

code based on whether or not ssh command is successful or not) ? I
really

want to know whether the command Chef::knife::Bootstrap.run (which
calls

Chef::knife::Ssh.run) is successful or not, so I can perform next
step based

on the result.

Thanks & Best Regards,
Hui Hu