ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-13681) Changing "Skip service check failure" and "Skip slave component failure" options after RU is kicked off does not work
Date Mon, 02 Nov 2015 18:27:27 GMT
Nate Cole created AMBARI-13681:
----------------------------------

             Summary: 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


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