[ 
https://issues.apache.org/jira/browse/AMBARI-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055232#comment-15055232
 ] 

Hadoop QA commented on AMBARI-14362:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12777364/1.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/4588//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/4588//console

This message is automatically generated.

> Express Upgrade: Kafka broker restart failed during EU from 2.2.9 to 2.3.2 
> with customized service user accounts
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14362
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14362
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>         Attachments: 1.patch
>
>
> *Steps:*
> Setup HDP 2.2.9 cluster with Ambari build #2.2.0.0-1281; the cluster has HA 
> enabled and setup with customized service users for all services
> Did EU from HDP 2.2.9 to 2.3.2.0
> Result:
> Observed during EU that Kakfa broker restart failed on all hosts with error:
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py",
>  line 101, in <module>
> KafkaBroker().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 496, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py",
>  line 88, in stop
> user=params.kafka_user,
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 154, in __init__
> self.env.run()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 158, in run
> self.run_action(resource, action)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 121, in run_action
> provider_action()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'source 
> /usr/hdp/current/kafka-broker/config/kafka-env.sh; 
> /usr/hdp/current/kafka-broker/bin/kafka stop' returned 1. Stopping Kafka 
> [23359] /usr/hdp/current/kafka-broker/bin/kafka: line 110: 
> /var/log/kafka/kafka.out: Permission denied
> failed.
> {code}
> The problem is likely due to custom service user being used for Kafka



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

Reply via email to