[
https://issues.apache.org/jira/browse/OOZIE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091035#comment-14091035
]
Robert Kanter commented on OOZIE-1920:
--------------------------------------
That's fine; we unfortunately still have some flakey tests it seems. These
test failures look unrelated to your patch. And you're correct, we ignore the
line length limit for queries (the script that checks this doesn't check for
that).
+1
> Capture Output for SSH Action doesn't work
> ------------------------------------------
>
> Key: OOZIE-1920
> URL: https://issues.apache.org/jira/browse/OOZIE-1920
> Project: Oozie
> Issue Type: Bug
> Components: action
> Affects Versions: 4.0.0
> Environment: CDH 5.0.2
> Reporter: Alessandro Costantino
> Assignee: Richard Williams
> Priority: Blocker
> Labels: cloudera, oozie, ssh
> Fix For: 4.1.0
>
> Attachments: OOZIE-1920.patch, OOZIE-1920.patch.2
>
>
> Running a simple workflow that have a shell action with capture-output
> enabled, the SShActionExecutor look at the wrong stdout file. This is the the
> command that I found in the log:
> ssh -o PasswordAuthentication=no -o KbdInteractiveDevices=no -o
> StrictHostKeyChecking=no -o ConnectTimeout=20 workflow@redhat5 cat
> oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing--ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@1.stdout
> But the generated stdout file is
> `/home/instadoc/oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing--ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@0.stdout`
> If you relaunch the action the ID that prepend the .stdout extension could
> vary (ie: @9.stdout, @4.stdout) but the SShActionExecutor looks always at
> @0.stdout.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
