[
https://issues.apache.org/jira/browse/AMBARI-23382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416167#comment-16416167
]
David F. Quiroga commented on AMBARI-23382:
-------------------------------------------
Starting work on this. But don't think I have access to assign to myself or
update status.
> Ambari-server sync-ldap: Sync event creation failed
> ---------------------------------------------------
>
> Key: AMBARI-23382
> URL: https://issues.apache.org/jira/browse/AMBARI-23382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.3, trunk, 2.6.2
> Reporter: David F. Quiroga
> Priority: Minor
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> As described here [ambari-server sync-ldap no longer
> working|https://community.hortonworks.com/questions/119756/ambari-server-sync-ldap-no-longer-working.html]
> sync-ldap fails with
> {{REASON: Sync event creation failed. Error details: hostname '127.0.0.1'
> doesn't match }}
> As pointed out by [Berry Osterlund
> |https://community.hortonworks.com/users/13196/berryosterlund.html]this is
> because the default behavior for ssl cert verification changed in python
> 2.7.5-58.
>
> ambari_server/serverUtils.py hardcodes "SERVER_API_HOST = '127.0.0.1'"
> Thinking we can provide the full hostname dyanmically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
