[
https://issues.apache.org/jira/browse/AMBARI-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283050#comment-14283050
]
Hudson commented on AMBARI-9183:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1532 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1532/])
AMBARI-9183. Rollling Upgrade - Server bootstrap creates incorrect repo version
(Yurii Shylov via ncole) (ncole:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fe3f405fadeafec62e2e257a60342fe7ebe52484)
*
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
*
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostVersionDAO.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
> 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)