[jira] [Commented] (AMBARI-14281) EU/RU can fail if register a repo without a build number that already exists, add PreCheck

["Alejandro Fernandez (JIRA)" <ji...@apache.org>]

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

Alejandro Fernandez commented on AMBARI-14281:
----------------------------------------------

This was inadvertently already committed to branch-2.2 in 8ddca83a5143623e84c4c6bd22b10df72f320221
and unit test was fixed in AMBARI-14235

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