[
https://issues.apache.org/jira/browse/AMBARI-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677656#comment-15677656
]
Hudson commented on AMBARI-18935:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6049 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6049/])
AMBARI-18935: 'HAWQ segments unregistered' shows incorrect alert (matt:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8b0939355612f331da3d1b029dc2878f2267c1b2])
* (edit)
ambari-server/src/test/python/common-services/HAWQ/test_alert_segment_registration_status.py
* (edit)
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/alerts/alert_segment_registration_status.py
> 'HAWQ segments unregistered' shows incorrect alert
> --------------------------------------------------
>
> Key: AMBARI-18935
> URL: https://issues.apache.org/jira/browse/AMBARI-18935
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Reporter: Matt
> Assignee: Matt
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18935-trunk-orig.patch
>
>
> The alert is caused because of the mismatch in case between HAWQ segment
> hostnames mentioned in the slaves file and the data stored in the DB
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
