You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/09/08 13:14:21 UTC
[jira] [Commented] (AMBARI-18340) Kafka acls setup is failing as
part of atlas start
[ https://issues.apache.org/jira/browse/AMBARI-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473832#comment-15473832 ]
Hadoop QA commented on AMBARI-18340:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12827542/AMBARI-18340.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{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/8610//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8610//console
This message is automatically generated.
> Kafka acls setup is failing as part of atlas start
> --------------------------------------------------
>
> Key: AMBARI-18340
> URL: https://issues.apache.org/jira/browse/AMBARI-18340
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.4.1
> Reporter: Ayub Khan
> Assignee: Ayub Khan
> Fix For: 2.4.1
>
> Attachments: AMBARI-18340.patch
>
>
> As part of AMBARI-18321, kafka-acls setup is added and it is failing.
> {noformat}
> 2016-09-08 06:16:23,280 - Execute['kinit -kt /etc//keytabs/hbase.headless.keytab hbase@EXAMPLE.COM; cat /var/lib/ambari-agent/tmp/atlas_hbase_setup.rb | hbase shell -n'] {'tries': 5, 'user': 'hbase', 'try_sleep': 10}
> 2016-09-08 06:16:31,867 - Execute['kinit -kt /etc//keytabs/kafka.service.keytab kafka/atlas-secure-no-ranger-2.openstacklocal@EXAMPLE.COM; bash /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh'] {'tries': 5, 'user': 'kafka', 'try_sleep': 10}
> 2016-09-08 06:16:32,016 - Retrying after 10 seconds. Reason: Execution of 'kinit -kt /etc//keytabs/kafka.service.keytab kafka/atlas-secure-no-ranger-2.openstacklocal@EXAMPLE.COM; bash /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh' returned 127. bash: /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh: No such file or directory
> 2016-09-08 06:16:42,219 - Retrying after 10 seconds. Reason: Execution of 'kinit -kt /etc//keytabs/kafka.service.keytab kafka/atlas-secure-no-ranger-2.openstacklocal@EXAMPLE.COM; bash /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh' returned 127. bash: /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh: No such file or directory
> 2016-09-08 06:16:52,429 - Retrying after 10 seconds. Reason: Execution of 'kinit -kt /etc//keytabs/kafka.service.keytab kafka/atlas-secure-no-ranger-2.openstacklocal@EXAMPLE.COM; bash /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh' returned 127. bash: /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh: No such file or directory
> 2016-09-08 06:17:02,642 - Retrying after 10 seconds. Reason: Execution of 'kinit -kt /etc//keytabs/kafka.service.keytab kafka/atlas-secure-no-ranger-2.openstacklocal@EXAMPLE.COM; bash /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh' returned 127. bash: /var/lib/ambari-agent/tmp/atlas_kafka_acl.sh: No such file or directory
> 2016-09-08 06:17:12,839 - Execute['source /etc/atlas/conf/atlas-env.sh ; /usr/hdp/current/atlas-server/bin/atlas_start.py'] {'not_if': 'ls /var/run/atlas/atlas.pid >/dev/null 2>&1 && ps -p `cat /var/run/atlas/atlas.pid` >/dev/null 2>&1', 'user': 'atlas'}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)