ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10467) UPGRADE: Due to changes in Ambari API some response validations should be allowed with warning message
Date Tue, 14 Apr 2015 15:19:13 GMT

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

Hadoop QA commented on AMBARI-10467:
------------------------------------

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

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> UPGRADE: Due to changes in Ambari API some response validations should be allowed with
warning message
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10467
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10467
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0, 2.0.1
>
>         Attachments: AMBARI-10467.branch-2.0.maint.patch, AMBARI-10467.patch
>
>
> upgradeHelper use well old realization of curl via shell execute. And to handle response
errors use some kind of validation of response. For new releases of Ambari response content
could be changed from time to time. We need to add some "soft" validation without generation
error and just warn user about unexpected response.



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

Mime
View raw message