[
https://issues.apache.org/jira/browse/OOZIE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454406#comment-13454406
]
Hadoop QA commented on OOZIE-739:
---------------------------------
Testing JIRA OOZIE-739
Cleaning local svn workspace
{code}
----------------------------
+1 PATCH_APPLIES
CLEAN cleaned target directories
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch does adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 910
Tests failures: 0
Tests errors: 0
+1 DISTRO
+1 distro tarball builds with the patch
----------------------------
{code}
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/99/
> a coord action fails because the uri points to a namenode that is not in
> whitelist. the E0901 error shows in the oozie.log, but not written to the
> database
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-739
> URL: https://issues.apache.org/jira/browse/OOZIE-739
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: trunk
> Reporter: Mohamed Battisha
> Assignee: Mona Chitnis
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-739v2.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> a coord action fails because the uri points to a namenode that is not in
> whitelist. the E0901 error shows in the oozie.log. but the error code and
> error
> message does not display in oozie job -info action# -verbose. for example,
> $ oozie job -log 0000028-100625200833755-oozie-oozi-C
> ...
> 2010-06-28 18:50:56,502 DEBUG CoordActionInputCheckCommand:544 - USER[mchiang]
> GROUP[users] TOKEN[] APP[coord-21-20]
> JOB[0000028-100625200833755-oozie-oozi-C]
> ACTION[-] checking for the file
> 2010-06-28 18:50:56,502 WARN CoordActionInputCheckCommand:541 - USER[mchiang]
> GROUP[users] TOKEN[] APP[coord-21-20]
> JOB[0000028-100625200833755-oozie-oozi-C]
> ACTION[-] 0000028-100625200833755-oozie-oozi-C@1: Exception occurs:
> java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
> Namenode [XXXXX:8020] not allowed, not in Oozies
> whitelist STORE is active true
> java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
> Namenode [XXXXX:8020] not allowed, not in Oozies
> whitelist
> ...
> $ oozie job -info 0000028-100625200833755-oozie-oozi-C@1 -verbose
> ID : 0000028-100625200833755-oozie-oozi-C@1
> ------------------------------------------------------------------------------------------------------------------------------------
> Action Number : 1
> Console URL : -
> Error Code : -
> Error Message : -
> External ID : -
> External Status : -
> Job ID : 0000028-100625200833755-oozie-oozi-C
> Tracker URI : -
> Created : 2010-06-28 18:50
> Status : WAITING
> Last Modified : 2010-06-28 18:50
> Missing Dependencies :
> hdfs://XXXXX/_SUCCESS
> ------------------------------------------------------------------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
