[AMBARI-18877] Ambari change hcat.proxy.hosts value during add service

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 2.5.0
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 14/Nov/16 17:28
• Updated: 16/Nov/16 16:45
• Resolved: 15/Nov/16 11:11

Description

Whenever user adds service to Ambari, the value "hadoop.proxyuser.hcat.hosts" got changed. We should either prompt user if he is comfortable with the changes, or let it alone. In customer environment, this values got changed to something different when he adds Accumulo, Kafka and Knox.

After the initial install, the property hadoop.proxyuser.hcat.hosts = '*'
Then, Accumulo was installed using the Ambari Add Service Wizard. After Accumulo was installed, the value of hadoop.proxyuser.hcat.hosts was 'baron2.example.org' (FQDN of second master node)
Then, Kafka was added using the Ambari Add Service Wizard. After Kafka was installed, the value of hadoop.proxyuser.hcat.hosts was "baron1.example.org,baron2.example.org".
Then Knox was added using the Ambari Add Service Wizard. After Knox was installed, the value of hadoop.proxyuser.hcat.hosts was 'baron1.example.org'. At this point the Hive Service Check failed with an "Unauthorized connection for super-user: hcat" error. "

In the support lab, value was set to hcat host after cluster installation. I changed it to * to match customer environments, and every time I add services it changed it back to hcat host

BUSINESS IMPACT: If customer is using Ambari view or Hue, changing this configuration will break them

Issue Links

• links to: review_request_