[
https://issues.apache.org/jira/browse/AMBARI-14944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134781#comment-15134781
]
Hadoop QA commented on AMBARI-14944:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12786492/AMBARI-14944.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 4 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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5235//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5235//console
This message is automatically generated.
> Refactor how reported versions are handled
> ------------------------------------------
>
> Key: AMBARI-14944
> URL: https://issues.apache.org/jira/browse/AMBARI-14944
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14944.patch
>
>
> Need to revisit how reported versions affect RU/SWU/PU. With PU, the version
> returned is not going to be the same as the other components in the cluster.
> This means when a version is reported, we must check that against the repo
> version that it's for, and save the actual_version in the hostcomponent
> "standard" data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
