[
https://issues.apache.org/jira/browse/AMBARI-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343138#comment-15343138
]
Shi Wang commented on AMBARI-11999:
-----------------------------------
Hi,
I think this has been fixed in 2.2, in my generated blueprint there is no kdc
server info anymore and need to add manually to blueprint a new cluster.
> Blueprint export incorrectly includes Kerberos host information
> ---------------------------------------------------------------
>
> Key: AMBARI-11999
> URL: https://issues.apache.org/jira/browse/AMBARI-11999
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The Blueprint processor incorrectly includes some Kerberos-related hostname
> properties in an exported Blueprint. Since there is no support yet for
> starting a Kerberized cluster directly with a Blueprint, these properties are
> confusing to users, and also include hostname information, which makes the
> Blueprint less portable across different cluster types.
> Steps to reproduce:
> 1. Setup a single-node cluster (HDFS/Yarn/Zookeeper/Metrics) with the Ambari
> UI.
> 2. Enable Kerberos using the Kerberos Wizard in the Ambari UI.
> 3. Export a Blueprint from the running cluster using the following REST URL:
> http://host:port/api/v1/clusters/cluster_name?format=blueprint
> This Blueprint will include the following Kerberos hostname properties:
> "admin_server_host" in "kerberos-env"
> "kdc_host" in "kerberos-env"
> "hadoop.proxyuser.yarn.hosts" in "core-site"
> The Blueprints configuration processor needs to updated to filter out these
> properties, or export them without the hostname information.
> I'm working on a fix for this, and will submit a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
