ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11251) serverUtils.py is not using customized client.api.port in ambari.properties
Date Wed, 20 May 2015 16:31:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-11251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552616#comment-14552616
] 

Hudson commented on AMBARI-11251:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2658 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2658/])
AMBARI-11251 - serverUtils.py is not using customized client.api.port in ambari.properties
(tbeerbower) (tbeerbower: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=444faa1e9bf5005ac26b1deccb727ac0a55bf5da)
* ambari-server/src/test/python/TestServerUtils.py
* ambari-server/src/test/python/TestServerUpgrade.py
* ambari-server/src/main/python/ambari_server/serverUtils.py
* ambari-server/src/test/python/TestAmbariServer.py


> serverUtils.py is not using customized client.api.port in ambari.properties
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-11251
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11251
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 2.1.0
>
>
> In customized ambari.properties file, client.api.port=8033. 
> When running command "#ambari-server sync-ldap --all -v" and find the output still shows
Ambari is syncing with " 127.0.0.1:8080 "
> It uses a hard coded value for the port.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message