[
https://issues.apache.org/jira/browse/AMBARI-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048531#comment-15048531
]
Hadoop QA commented on AMBARI-14281:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12776469/AMBARI-14281.trunk.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4532//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4532//console
This message is automatically generated.
> EU/RU can fail if register a repo without a build number that already exists,
> add PreCheck
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-14281
> URL: https://issues.apache.org/jira/browse/AMBARI-14281
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.2.0
>
> Attachments: AMBARI-14281.trunk.patch
>
>
> If a cluster has version x (e.g., HDP 2.3.2.0-2950) as CURRENT, and the user
> registers a Repository Version such as 2.3.xx that uses different build URLs
> but results in the same build number, then installing packages will be a
> no-op.
> This means that no new version will be detected using the "deltas" method and
> the repo_version entity will keep the "version" field without a build number,
> and the Cluster Version entity will transition into INSTALLED (since
> technically it is already installed).
> This incorrect setup will allow the user to start a RU/EU, which will
> immediately fail since the Repo Version has no build number, which is needed
> by hdp-select.
> The fix is to add a PreCheck that ensures that all repos contain a build
> number.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
