On Wednesday, May 2, 2012 at 2:51 AM, AJ Christensen wrote:
The feature sounds so incredibly useless you may have to contribute ityourself. Even then I'd be dubious about it being accepted apart fromsolely as a bug fix.You do not need an SSH-as-a-framework system.--AJOn 2 May 2012 20: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).-- MOn 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
Archive powered by MHonArc 2.6.16.