[
https://issues.apache.org/jira/browse/AMBARI-16125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260577#comment-15260577
]
Hudson commented on AMBARI-16125:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4748 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4748/])
AMBARI-16125. 500-error on PUT to the repository_versions endpoint (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bff239c08cb0409898f71c764c0514c03b0ca087])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
> 500-error on PUT to the repository_versions endpoint
> ----------------------------------------------------
>
> Key: AMBARI-16125
> URL: https://issues.apache.org/jira/browse/AMBARI-16125
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 2.4.0
>
> Attachments: AMBARI-16125.patch
>
>
> RepositoryVersionResourceProvider would check the version being
> created/updated was able to be a target for upgrade. This logic is now
> incorrect as we can create versions with no cluster installed at all. There
> are other places that check compatibility and is unnecessary in the provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
