ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12853) Manual registration of non root ambari agent with two way ssl authentication failed
Date Fri, 21 Aug 2015 18:21:46 GMT

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

Hudson commented on AMBARI-12853:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #407 (See [https://builds.apache.org/job/Ambari-branch-2.1/407/])
AMBARI-12853 Manual registration of non root ambari agent with two way ssl authentication
failed (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=43bea329425d1ee936871986c2185d9ffd57c085)
* ambari-agent/conf/unix/ambari-agent


> Manual registration of non root ambari agent with two way ssl authentication failed
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-12853
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12853
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-agent
>    Affects Versions: 2.1.1
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12853.patch
>
>
> nstall ambari-server
> Generate necessary certificates and setup ambari two way ssl authentication.
> Install ambari-agent on hosts.
> Configure ambari-agent to run under non root user.
> Try manual host registration.
> IOError: Request to 
> https://192.168.64.101:8441/agent/v1/register/c6402.ambari.apache.org failed due to [Errno
13] Permission denied: '/var/lib/ambari-agent/keys/ca.crt'
> /var/lib/ambari-agent/keys is created when package is installed and has root owner, so
when ambari-agent is running under non-root it is not able to write to that dir.
> Should I chown that dir when configuring non root agents? Or agent itself should manage
that dir?



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

Mime
View raw message