[ https://issues.apache.org/jira/browse/OOZIE-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493534#comment-16493534 ]
Hadoop QA commented on OOZIE-3156: ---------------------------------- Testing JIRA OOZIE-3156 Cleaning local git workspace ---------------------------- {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} . {color:green}+1{color} the patch does not introduce any @author tags . {color:green}+1{color} the patch does not introduce any tabs . {color:green}+1{color} the patch does not introduce any trailing spaces . {color:red}-1{color} the patch contains 1 line(s) longer than 132 characters . {color:red}-1{color} the patch does not add/modify any testcase {color:green}+1 RAT{color} . {color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} {color:green}+1 JAVADOC{color} . {color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) . {color:green}+1{color} the patch does not seem to introduce new Javadoc error(s) . {color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s) {color:green}+1 COMPILE{color} . {color:green}+1{color} HEAD compiles . {color:green}+1{color} patch compiles . {color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [webapp]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [client]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} . {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations . {color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} . Tests run: 2132 . {color:orange}Tests failed at first run:{color} TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3 . For the complete list of flaky tests, see TEST-SUMMARY-FULL files. {color:green}+1 DISTRO{color} . {color:green}+1{color} distro tarball builds with the patch ---------------------------- {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/586/ > SSH action status turns OK wrongly when failed to connect to host > ----------------------------------------------------------------- > > Key: OOZIE-3156 > URL: https://issues.apache.org/jira/browse/OOZIE-3156 > Project: Oozie > Issue Type: Bug > Components: action > Affects Versions: 5.0.0 > Reporter: TIAN XING > Assignee: TIAN XING > Priority: Major > Attachments: ssh-check-bug.patch > > > When {{check()}} method of {{SshActionExecutor}} gets invoked, oozie will ssh > connect to the host and check whether the pid of the process that ssh action > started is still there (by checking the returned value of command "{{ssh > <host-ip> ps -p <pid>}}" ) to determine whether ssh action completes or not. > However, we found cases where oozie fails to connect to host during action > status check (e.g., the host is under heavy load, or network is bad etc.). > In such cases, the return value of command "{{ssh <host-ip> ps -p <pid>}}" > will be 255 (ssh command exits with the exit status of the remote command or > with 255 if an error occurred.). > According the current logic of method {{getActionStatus()}} in > {{SshActionExecutor}}, the action status will be determined as OK which may > not be correct. -- This message was sent by Atlassian JIRA (v7.6.3#76005)