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

Hadoop QA commented on AMBARI-18774:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12836610/AMBARI-18774.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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.controller.metrics.JMXPropertyProviderTest

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

This message is automatically generated.

> Install Package for non-HDP stack fails with non-VDF repo version
> -----------------------------------------------------------------
>
>                 Key: AMBARI-18774
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18774
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>            Priority: Critical
>             Fix For: 2.4.2
>
>         Attachments: AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

Reply via email to