[
https://issues.apache.org/jira/browse/AMBARI-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317067#comment-14317067
]
Hadoop QA commented on AMBARI-9576:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12698146/AMBARI-9576.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1645//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1645//console
This message is automatically generated.
> LDAP Sync: Port and Protocol hard coded /usr/sbin/ambari-server.py
> ------------------------------------------------------------------
>
> Key: AMBARI-9576
> URL: https://issues.apache.org/jira/browse/AMBARI-9576
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 2.0.0
>
> Attachments: AMBARI-9576.patch
>
>
> PROBLEM: User is unable to ldap sync with ambari server and LDAP SSL
> configured.
> It appears that /usr/sbin/ambari-server.py has the port of the api hard coded.
> {code}
> root@ml-ambari /var/log>ambari-server sync-ldap --all -v
> Using python /usr/bin/python2.6
> Syncing with LDAP...
> INFO: about to run command: ps -p 54735
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Enter Ambari Admin login: rayoung
> Enter Ambari Admin password:
> Syncing all.
> Calling API /api/v1/ldap_sync_events : [{'Event': {'specs':
> [{'principal_type': 'users', 'sync_type': 'all'}, {'principal_type':
> 'groups', 'sync_type': 'all'}]}}]
> ERROR: Exiting with exit code 1.
> REASON: Sync event creation failed. Error details: <urlopen error [Errno 111]
> Connection refused>
> {code}
> It can be worked around by manually editing ...
> {code}
> SERVER_API_PROTOCOL = 'http'
> SERVER_API_PORT = '8080'
> {code}
> in the python script or by turning off SSL and restarting Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
