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

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-16125:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12800860/AMBARI-16125.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.agent.TestHeartbeatHandler

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6679//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6679//console

This message is automatically generated.

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