You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/09/10 05:27:10 UTC
[jira] [Closed] (OOZIE-186) GH-208: Initialization of FS instances
are wrong in many places and fail with Kerberos
[ https://issues.apache.org/jira/browse/OOZIE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-186.
----------------------------------
Resolution: Fixed
> GH-208: Initialization of FS instances are wrong in many places and fail with Kerberos
> --------------------------------------------------------------------------------------
>
> Key: OOZIE-186
> URL: https://issues.apache.org/jira/browse/OOZIE-186
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Empty configurations are used/propagated and this causes Oozie to fail when Kerberos is ON.
> Testcases fail depending on the order they are executed. If a FS is already in the cache with the right values, things are OK, otherwise, they fail.
> This creates a difficult to trace problem.
> It seems related to to Configuration initialization (mostly for testcases) where the K principal rules are not present.
> Coordinator commands have several issues on this regard.
> Addressing the ones that I'm finding now in this patch with minimal changes.
> However, commands logic must be done properly as part of refactorying/cleanup
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira