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

Hudson commented on AMBARI-20843:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7363 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7363/])
AMBARI-20843. Client configs downloaded via Ambari are empty with (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=101942df479c7e572eb3c5c984eef0903b44d05c])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
* (edit) 
ambari-common/src/main/python/resource_management/libraries/script/script.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_hdfs_client.py


> Client configs downloaded via Ambari are empty with non-root ambari-server
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-20843
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20843
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20843.patch
>
>
>   * Deploy HA cluster with Ambari-2.5.1.0-24 bits with HDP-2.6.1.0 
> (reproducible with HDP-2.6.0.3 as well).
>   * Try to download client configs from Ambari ui - from Service Actions 
> dropdown or Download All Client configs in Actions dropdown or from Hosts page
>   * It downloads tar file but file seems to be empty.  
> Please help take a look.  
> Artifacts of this run can be found [here](http://qelog.hortonworks.com/log
> /nat-yc-r6-gyas-ambari-config-5/test-logs/ambari-config/artifacts/screenshots/
> com.hw.ambari.ui.tests.monitoring.TestDownloadConfigurations/testA_DownloadCli
> entConfigurationsOnServicesTab/_18_13_54_43_Downloaded_Archive_from_Service_pa
> ge__tmp_YARN_CLIENT_configs_tar_gz_have_not_same_coun/)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to