[ https://issues.apache.org/jira/browse/AMBARI-23382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431087#comment-16431087 ]
Hudson commented on AMBARI-23382: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9020 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9020/]) [AMBARI-23382] Ambari-server sync-ldap: Sync event creation failed (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=674807e82eb1ee2187a28947f007d8afabf373c6]) * (edit) ambari-server/src/test/python/TestAmbariServer.py * (edit) ambari-server/src/main/python/ambari_server/serverUtils.py * (edit) ambari-server/src/test/python/TestServerUtils.py > 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.6.1, trunk, 2.6.2 > Environment: Python 2.7.5-58 or greater > Reporter: David F. Quiroga > Priority: Minor > Labels: pull-request-available > Original Estimate: 4h > Time Spent: 1h 10m > Remaining Estimate: 2h 50m > > 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)