[jira] [Commented] (AMBARI-9183) Rollling Upgrade - Server bootstrap creates incorrect repo version

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

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

Hadoop QA commented on AMBARI-9183:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12692804/AMBARI-9183.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 1 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 test build failed in ambari-server 

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

This message is automatically generated.

> Rollling Upgrade - Server bootstrap creates incorrect repo version
> ------------------------------------------------------------------
>
>                 Key: AMBARI-9183
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9183
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Yurii Shylov
>            Assignee: Yurii Shylov
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9183.patch
>
>
> Currently on clean install Ambari creates cluster entity and its repository version with version taken from selected stack. I.e. for stack HDP-2.2, version 2.2 is written to database, without any information about the actual minor version of that stack. Besides that we can't assume that cluster has some version until it has at least one of components of that version.
> Repository version creation should be detached from cluster creation; instead of that versions should be created after receiving the first actual version from service responses during install.



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