[
https://issues.apache.org/jira/browse/AMBARI-13748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995151#comment-14995151
]
Hadoop QA commented on AMBARI-13748:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12771076/AMBARI-13748.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4204//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4204//console
This message is automatically generated.
> Being able to clean repository cache before installing open source components
> -----------------------------------------------------------------------------
>
> Key: AMBARI-13748
> URL: https://issues.apache.org/jira/browse/AMBARI-13748
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server
> Affects Versions: 2.1.0
> Reporter: Di Li
> Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-13748.patch
>
>
> Need a way for Ambari to trigger a repository clean (yum clean expire-cache,
> for example) when updating repository files during an Ambari update as well
> as fresh installation of a cluster.
> Currently, this must be done occasionally through a manual step, and if not
> done will lead to problems during install.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
