[AMBARI-11999] Blueprint export incorrectly includes Kerberos host information

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Component/s: ambari-server
• Assignee: Bob Nettleton
• Reporter: Bob Nettleton
• Created: 18/Jun/15 14:32
• Updated: 22/Jun/16 01:04

Description

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.