You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "John Speidel (JIRA)" <ji...@apache.org> on 2014/09/23 17:35:35 UTC

[jira] [Resolved] (AMBARI-7368) Hostnames not properly masked in an exported blueprint

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

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

merged to trunk

> Hostnames not properly masked in an exported blueprint
> ------------------------------------------------------
>
>                 Key: AMBARI-7368
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7368
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.6.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 1.7.0
>
>
> Some properties that include host name information are not properly masked during a blueprint export of a running cluster.
> Most of the properties that are not masked properly are related to NameNode HA or Kerberos setup
> To reproduce:
> 1. Start an HDP cluster with the Ambari UI
> 2. Use the Ambari Wizard to enable NameNode HA once the cluster is up and running.
> 3. Use the Ambari Wizard to enable Kerberos security once the cluster is up and running. 
> 4. Use the REST API to export a blueprint of this running cluster, and some hostnames will appear in the configuration.
> The hostnames in the exported blueprint should be masked, since the blueprint should not contain any specific hostnames, in order to be more generic and applicable to various cluster creation templates.  
> I'm working on a patch to resolve this, and will be submitting the patch shortly.  



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