[
https://issues.apache.org/jira/browse/OOZIE-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685486#comment-15685486
]
Hadoop QA commented on OOZIE-2742:
----------------------------------
Testing JIRA OOZIE-2742
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:green}+1{color} the patch does not introduce any line longer than
132
. {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{color} the patch does not seem to introduce new Javadoc
warnings
{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:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting.
{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:red}-1 TESTS{color}
. Tests run: 1831
. Tests failed: 3
. Tests errors: 0
. The patch failed the following testcases:
.
testBundleStatusCoordSubmitFails(org.apache.oozie.service.TestStatusTransitService)
.
testActionKillCommandActionNumbers(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
.
testMaxMatThrottleNotPicked(org.apache.oozie.service.TestCoordMaterializeTriggerService)
{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/oozie-trunk-precommit-build/3455/
> Unable to kill applications based on tag
> ----------------------------------------
>
> Key: OOZIE-2742
> URL: https://issues.apache.org/jira/browse/OOZIE-2742
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
> Attachments: OOZIE-2742-1.patch
>
>
> We set the scope to OWN while requesting the applications.
> [here|https://github.com/apache/oozie/blob/master/hadooplibs/hadoop-utils-2/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java#L70]
> Yarn checks if application is owned by the requester.
> [here|https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ClientRMService.java#L906-L907]
> Owner of oozie process is the requester.
> But, application owner can be different from the owner of oozie process. We
> need to set scope to ALL.
> If we set scope to VIEWABLE and if user is setting view acl list on the
> application, then he/she need to include oozie process owner all the time,
> which sounds painful for user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
