You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/02/02 16:20:00 UTC
[jira] [Commented] (AMBARI-22889) LDAP configuration is not
reloaded in Guice
[ https://issues.apache.org/jira/browse/AMBARI-22889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350600#comment-16350600 ]
Hudson commented on AMBARI-22889:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8673/])
[AMBARI-22889] LDAP configuration is not reloaded in Guice (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=40549ef9ae0b16b292c8b462acdbb52306acb2d6])
* (edit) ambari-server/src/test/python/TestAmbariServer.py
* (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDuplicateUserTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/ldap/service/AmbariLdapConfigurationProvider.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderTest.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDNWithSpaceTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProvider.java
> 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
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> +*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)