ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13681) Changing "Skip service check failure" and "Skip slave component failure" options after RU is kicked off does not work
Date Tue, 03 Nov 2015 17:29:28 GMT

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

Hudson commented on AMBARI-13681:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #790 (See [https://builds.apache.org/job/Ambari-branch-2.1/790/])
AMBARI-13681. Changing 'Skip service check failure' and 'Skip slave (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c4bc11e0d7956f5234b54fcbd53c14e30550d620])
* 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/dao/HostRoleCommandDAO.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java


> Changing "Skip service check failure" and "Skip slave component failure" options after
RU is kicked off does not work
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13681
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13681
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13681.patch
>
>
> RU was kicked off with both skip options turned on.
> It correctly skipped service check and slave component failures.
> In the middle of RU (during Core Slaves), these options were turned off.
> Verified by making a GET call to the upgrades/upgrade_id endpoint to make sure that the
server has persisted:
> {noformat}
> ...
> skip_failures: false,
> skip_service_check_failures: false,
> ...
> {noformat}
> However, subsequent failures in the same upgrade group Core Slaves were skipped (incorrect).
> Also, service check failures were ignored in subsequent "All Service Checks" upgrade
groups.



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

Mime
View raw message