[ https://issues.apache.org/jira/browse/AMBARI-21347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064605#comment-16064605 ]
Hudson commented on AMBARI-21347: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1635 (See [https://builds.apache.org/job/Ambari-branch-2.5/1635/]) 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=dd250992acd3c541f325ab0c30673bfc49176fda]) * (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)