[
https://issues.apache.org/jira/browse/AMBARI-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664757#comment-15664757
]
Hadoop QA commented on AMBARI-18877:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838801/AMBARI-18877.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9259//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9259//console
This message is automatically generated.
> Ambari change hcat.proxy.hosts value during add service
> -------------------------------------------------------
>
> Key: AMBARI-18877
> URL: https://issues.apache.org/jira/browse/AMBARI-18877
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.1
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18877.patch
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
