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

Hudson commented on AMBARI-13524:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3706 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3706/])
AMBARI-13524 - Change a Request In Progress To Skip Errors Automatically 
(jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=502dc1862d974eb4c072864db0981a11bdfe4f66])
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAO.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAOTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostRoleCommandEntity.java


> Change a Request In Progress To Skip Errors Automatically
> ---------------------------------------------------------
>
>                 Key: AMBARI-13524
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13524
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.3
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.3
>
>
> Although the upgrade endpoint can be used to marked failures as being 
> automatically skipped:
> {code:title=POST api/v1/clusters/c1/upgrades}
> {
>   "Upgrade": {
>     "repository_version": "2.3.0.0-2545",
>     "skip_failures": true
>   }
> }
> {code}
> This currently does not work on upgrades already in progress. The API should 
> allow an upgrade in progress to have its stages altered so that they will 
> automatically skip failures. This would be a PUT command:
> {code:title=PUT api/v1/clusters/c1/upgrades/1}
> {
>   "Upgrade": {
>     "skip_failures": true
>   }
> }
> {code}



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

Reply via email to