[
https://issues.apache.org/jira/browse/AMBARI-21347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064575#comment-16064575
]
Hudson commented on AMBARI-21347:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7688 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7688/])
AMBARI-21347. Service Page: Some Alerts are missing their Status (smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9833bc182d9b44a69bb766de77311d4a3a50fa5e])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
> Service Page: Some Alerts are missing their Status
> --------------------------------------------------
>
> Key: AMBARI-21347
> URL: https://issues.apache.org/jira/browse/AMBARI-21347
> Project: Ambari
> Issue Type: Bug
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21347.patch
>
>
> On sysprepped environments In case of using provision_action START_ONLY,
> master components are already installed, hence no INSTALL command is
> generated, the state of ServiceComponentHost is set to INSTALLED. The problem
> is that alert definitions are triggered by ServiceComponentHost
> transitioning from INSTALLING --> INSTALLED.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
