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

Hadoop QA commented on AMBARI-8991:
-----------------------------------

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

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/1166//console

This message is automatically generated.

> Pre-Upgrade checks: validate cluster_name add repository_version properties
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-8991
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8991
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Yurii Shylov
>            Assignee: Yurii Shylov
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8991.patch
>
>
> The following requests:
> {code}/api/v1/clusters/1/rolling_upgrades_check/?fields=UpgradeChecks/repository_version{code}
> {code}/api/v1/clusters/1/rolling_upgrades_check/?UpgradeChecks/repository_version=2.99999&fields=*{code}
> {code}/api/v1/clusters/sdfdsfdsfdsf1/rolling_upgrades_check/?UpgradeChecks/repository_version=2.99999&fields=*{code}
> are generating error with "reason" : "Unexpected server error happened".
> These usecases should be checked explicitely



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to