[ 
https://issues.apache.org/jira/browse/AMBARI-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yurii Shylov updated AMBARI-9183:
---------------------------------
    Attachment: AMBARI-9183.patch

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

Reply via email to