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

2016-06-01 Thread Hudson (JIRA) 

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

Hudson commented on AMBARI-16933:
-

FAILURE: Integrated in Ambari-trunk-Commit #4979 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4979/])
AMBARI-16933. VDF should use package-version for the os, not the release 
(ncole: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7033b1c5490a61756727a517fd4a02ecce0c11d9])
* 
ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/RepositoryXml.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/repository/VersionDefinitionTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/repository/Release.java
* ambari-server/src/test/resources/hbase_version_test.xml


> 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)

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

2016-05-28 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)