ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12392) RU - Repo version should be unique within the stack
Date Tue, 14 Jul 2015 08:57:04 GMT

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

Hadoop QA commented on AMBARI-12392:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12745178/AMBARI-12392.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 11 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/3403//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3403//console

This message is automatically generated.

> RU - Repo version should be unique within the stack
> ---------------------------------------------------
>
>                 Key: AMBARI-12392
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12392
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Blocker
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12392.branch-2.1.patch, AMBARI-12392.patch
>
>
> STR:
> * Install HDP 2.2
> * Register repo for HDP 2.3, such as 2.3.0.0 and do not provide a build number
> * Install the package
> * Stop all components
> * SSH onto one host and begin a manual upgrade by calling "hdp-select set <comp>
2.3.0.0-####"
> * Start the component that was switched
> This happens because the build version, e.g, 2.3.0.0-2546, can be repeated multiple times
in the repo_version table, even for the same stack. 
> To fix this, we should enforce it to be unique.



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

Mime
View raw message