You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2016/04/26 19:45:13 UTC

[jira] [Updated] (AMBARI-16125) 500-error on PUT to the repository_versions endpoint

     [ https://issues.apache.org/jira/browse/AMBARI-16125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Cole updated AMBARI-16125:
-------------------------------
    Summary: 500-error on PUT to the repository_versions endpoint  (was: 500-error on PUT to the repository_versions)

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