[METRON-1400] Elasticsearch service check fails in Ambari

• Type: Bug
• Status: Done
• Priority: Major
• Resolution: Done
• Fix Version/s: 0.5.0
• Assignee: Michael Miklavcic
• Reporter: Michael Miklavcic
• Created: 12/Jan/18 16:10
• Updated: 21/May/19 20:18
• Resolved: 24/Jan/18 22:31

Description

This is service check, not to be confused with the status check. ie,

• service check = dropdown in Ambari service when you click "service actions"- there is an option labeled "service check" which does a more rigorous check on the service than simply an on/off check.
• status check = the green checkbox or red exclamation next to the service name in Ambari indicating if the thing is running.

stderr:
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/ELASTICSEARCH/5.6.2/package/scripts/service_check.py", line 77, in <module>
    ServiceCheck().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 329, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/ELASTICSEARCH/5.6.2/package/scripts/service_check.py", line 35, in service_check
    Logger.info("Running Elastic search service check", file=sys.stdout)
TypeError: info() got an unexpected keyword argument 'file'
 stdout:

Command failed after 1 tries

Issue Links

• links to: GitHub Pull Request #904