[
https://issues.apache.org/jira/browse/AMBARI-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394829#comment-14394829
]
Hudson commented on AMBARI-10349:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2198 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2198/])
AMBARI-10349. RU: Block users from installing a Version with the same existing
Version (dlysnichenko) (dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6b5ef474b0b43a4b8d9fa49b76ff55c85a04c52d)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
> RU: Block users from installing a Version with the same existing Version
> ------------------------------------------------------------------------
>
> Key: AMBARI-10349
> URL: https://issues.apache.org/jira/browse/AMBARI-10349
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-10349.patch
>
>
> When creating a Version, if a user accidentally, or unknowingly uses the same
> repo, or a repo that has RPM's with the same version as the current Version,
> it can be installed successfully. The result is that rolling upgrades will
> fail as the versions show up the same in hdp-select because the packages are
> the same.
> Validate either on Version "registration" or on attempted Version "install"
> that the software in the repository match an already existing registered
> version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
