[jira] [Created] (METRON-1172) Upgrade from Metron 0.4.1-rc to 0.4.1-rc4 'escalation' topic problem.

["Laurens Vets (JIRA)" <ji...@apache.org>]

Laurens Vets created METRON-1172:
------------------------------------

             Summary: Upgrade from Metron 0.4.1-rc to 0.4.1-rc4 'escalation' topic problem.
                 Key: METRON-1172
                 URL: https://issues.apache.org/jira/browse/METRON-1172
             Project: Metron
          Issue Type: Bug
    Affects Versions: 0.4.1
         Environment: Metron 0.4.1-rc4
            Reporter: Laurens Vets
            Priority: Minor


After upgrading from 0.4.1-rc (from last week) to rc4, both Metron Management UI and Metron REST fail to start with an error related to "METRON_ESCALATION_TOPIC="{{metron_escalation_topic}}"".

Metron Management UI Start output:

Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/scripts/management_ui_master.py", line 95, in <module>
    ManagementUIMaster().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 280, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/scripts/management_ui_master.py", line 67, in start
    self.configure(env)
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/scripts/management_ui_master.py", line 47, in configure
    content=Template("metron.j2")
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 123, in action_create
    content = self._get_content()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 160, in _get_content
    return content()
  File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", line 51, in __call__
    return self.get_content()
  File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", line 142, in get_content
    rendered = self.template.render(self.context)
  File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line 891, in render
    return self.environment.handle_exception(exc_info, True)
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/templates/metron.j2", line 42, in top-level template code
    METRON_ESCALATION_TOPIC="{{metron_escalation_topic}}"
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py", line 73, in __getattr__
    raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'metron_escalation_topic' was not found in configurations dictionary!

Metron REST Start output:

Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/scripts/rest_master.py", line 83, in <module>
    RestMaster().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 280, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/scripts/rest_master.py", line 55, in start
    self.configure(env)
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/scripts/rest_master.py", line 43, in configure
    content=Template("metron.j2")
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 123, in action_create
    content = self._get_content()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 160, in _get_content
    return content()
  File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", line 51, in __call__
    return self.get_content()
  File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", line 142, in get_content
    rendered = self.template.render(self.context)
  File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line 891, in render
    return self.environment.handle_exception(exc_info, True)
  File "/var/lib/ambari-agent/cache/common-services/METRON/0.4.1/package/templates/metron.j2", line 42, in top-level template code
    METRON_ESCALATION_TOPIC="{{metron_escalation_topic}}"
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py", line 73, in __getattr__
    raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'metron_escalation_topic' was not found in configurations dictionary!

After posting this on the mailing list, both [~cestella] and [~ottobackwards] came up with the solution:
The fix for right now is to update the Metron escalation topic setting in the Metron Config in ambari under "Metron REST" from the default "escalation" to something else, "metron_escalation" for instance. Afterwards, Metron REST & Management UI start without issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)