[
https://issues.apache.org/jira/browse/AMBARI-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153327#comment-15153327
]
Hadoop QA commented on AMBARI-15098:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12788513/AMBARI-15098.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5454//console
This message is automatically generated.
> Ambari Schema Version should ignore patch number from version number
> --------------------------------------------------------------------
>
> Key: AMBARI-15098
> URL: https://issues.apache.org/jira/browse/AMBARI-15098
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15098.patch
>
>
> # On ambari-server upgrade to a patch release version (2.0.2 -> 2.2.1.2),
> ambari server fails to start.
> # This is because the schema version set in the DB on ambari-server upgrade
> is 2.2.1 whereas ambari-server version is 2.2.1.2.
> # This incosistency leads to DB check failure. DB check should ignore patch
> release number from the ambari version.
> # Further a clean install on 2.2.1.2 will set the DB schema version to
> 2.2.1.2 whereas an upgrade to 2.2.1.2 will set the DB schema version to 2.2.1
> # We should fix this inconsistency by always setting DB schema version to
> 3-digit and ignoring the patch release version during DB check.
> # We will not be supporting DB schema changes in patch releases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
