[
https://issues.apache.org/jira/browse/AMBARI-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001289#comment-15001289
]
Hudson commented on AMBARI-13818:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3814 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3814/])
AMBARI-13818. SKIPPED_FAILED state should not be bubbled up to the
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=85647998806346379042535692349c1b492e4bf6])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CalculatedStatus.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CalculatedStatusTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeGroupResourceProvider.java
> 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
> Affects Versions: 2.1.3
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> 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)
