Sandor Molnar created AMBARI-22889:
--------------------------------------
Summary: LDAP configuration is not reloaded in Guice
Key: AMBARI-22889
URL: https://issues.apache.org/jira/browse/AMBARI-22889
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
+*Steps to reproduce:*+
run _ambari-server setup-ldap_ and set primary host:port to "myHost:1"
run _ambari-server sync-ldap --all_
+*Actual results:*+
the synch process will fail due to a CommunicationException saying that
*localhost:33389* is not reachable.
+*Expected results:*+
the synch process will fail due to a CommunicationException saying that
*myHost:1* is not reachable.
+*Additional information:*+
in ambari-server.log I saw that AmbariConfigurationChangedEvent has been
triggered and processed when setup-ldap updated the DB (see
org.apache.ambari.server.ldap.service.AmbariLdapConfigurationProvider; however
the get() method does not seem to be called when needed; it's maybe a Guice
injection scope issue)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
