[jira] [Commented] (AMBARI-16933) VDF should use package-version for the os, not the release

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-16933:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12806709/AMBARI-16933.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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7045//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7045//console

This message is automatically generated.

> VDF should use package-version for the os, not the release
> ----------------------------------------------------------
>
>                 Key: AMBARI-16933
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16933
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16933.patch
>
>
> The aggregated VDF skips package-version as it is defined in the {{release}} element.  This is incorrect as it implies that information is consistent for all repositories in the VDF.  The element has been moved, so code needs to account for that when formulating commands to the agent.



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