You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2015/11/10 18:26:11 UTC

[jira] [Updated] (AMBARI-13818) SKIPPED_FAILED state should not be bubbled up to the Upgrade level

     [ https://issues.apache.org/jira/browse/AMBARI-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko updated AMBARI-13818:
----------------------------------------
    Component/s: ambari-server

> SKIPPED_FAILED state should not be bubbled up to the Upgrade level
> ------------------------------------------------------------------
>
>                 Key: AMBARI-13818
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13818
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>         Attachments: AMBARI-13818.patch
>
>
> When there is a skipped failure, the "upgrade" state itself comes SKIPPED_FAILED. Even when the upgrade is running or paused, it is returning "SKIPPED_FAILED". The API should not roll this up to the "upgrade" level as the current behavior is confusing.  At the top level, it should just be HOLDING, IN_PROGRESS, COMPLETED, etc.  SKIPPED_FAILED should be bubbled up to the upgrade group level and stop there.



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