ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13818) SKIPPED_FAILED state should not be bubbled up to the Upgrade level
Date Tue, 10 Nov 2015 17:26:11 GMT

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

Dmitry Lysnichenko updated AMBARI-13818:
----------------------------------------
    Attachment: AMBARI-13818.patch

> 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)

Mime
View raw message