[jira] [Resolved] (AMBARI-7439) Proper metadata missing for Oozie password property in HDP 2.1 stack

["John Speidel (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-7439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Speidel resolved AMBARI-7439.
----------------------------------
    Resolution: Fixed

merged to trunk

> Proper metadata missing for Oozie password property in HDP 2.1 stack
> --------------------------------------------------------------------
>
>                 Key: AMBARI-7439
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7439
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.6.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 1.7.0
>
>
> The following Oozie password in the HDP 2.1 stack definition:
> oozie.service.JPAService.jdbc.password
> does not include all the correct metadata.  
> This field is marked as a password in the HDP 2.0.6 stack, but is mistakenly overridden in the 2.1 stack to not include this metadata.  
> This causes problems when a Blueprint is exported, since the oozie password field mentioned above is included in the export, which is not the desired behavior.  The Blueprint processing code uses the Stack definitions to determine which fields are passwords, in order to determine which fields to remove from an exported blueprint based on a running cluster.  
> The proper fix for this is to remove the password configuration definition in the 2.1 stack.  Since 2.1 inherits the configuration from 2.0.6, the password filed (and the correct metadata) can be inherited from the parent stack.
> I'm working on a patch to resolve this, and will submit the patch shortly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)