You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2016/06/06 14:13:21 UTC

[jira] [Created] (AMBARI-17059) Service stop/start fail after Ambari upgrade due to missing config parameters

Andrew Onischuk created AMBARI-17059:
----------------------------------------

             Summary: Service stop/start fail after Ambari upgrade due to missing config parameters
                 Key: AMBARI-17059
                 URL: https://issues.apache.org/jira/browse/AMBARI-17059
             Project: Ambari
          Issue Type: Bug
            Reporter: Andrew Onischuk
            Assignee: Andrew Onischuk
             Fix For: 2.4.0


ambari-server --hash  
43b564767ccf9eaa60f4e352c46ed3cb32dc7e78


Observed this issue in a couple of scenarios:

**Scenario #1**

  1. Deploy HDP-2.4.2.0 with Ambari 2.2.2.0
  2. Upgrade Ambari to 2.4.0.0-635 build
  3. Register HDP-2.5.0.0-639 and install the bits
  4. Start Express Upgrade to 2.5

Oozie server start failed with below error:

    
    
    
    Traceback (most recent call last):
      File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py", line 215, in <module>
        OozieServer().execute()
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 257, in execute
        method(env)
      File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py", line 100, in stop
        oozie_service(action='stop', upgrade_type=upgrade_type)
      File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk
        return fn(*args, **kwargs)
      File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py", line 149, in oozie_service
        stop_cmd  = format("cd {oozie_tmp_dir} && {oozie_home}/bin/oozie-stop.sh")
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py", line 95, in format
        return ConfigurationFormatter().format(format_string, args, **result)
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py", line 59, in format
        result_protected = self.vformat(format_string, args, all_params)
      File "/usr/lib64/python2.7/string.py", line 549, in vformat
        result = self._vformat(format_string, args, kwargs, used_args, 2)
      File "/usr/lib64/python2.7/string.py", line 582, in _vformat
        result.append(self.format_field(obj, format_spec))
      File "/usr/lib64/python2.7/string.py", line 599, in format_field
        return format(value, format_spec)
      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 'oozie_tmp_dir' was not found in configurations dictionary!
    

**Scenario #2**

  1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
  2. Upgrade Ambari to 2.4.0.0-635 build
  3. Delete Ranger service
  4. Restart all services with stale configs

**Result**  
ATS, DN, Falcon client restart fails with below error

    
    
    
    Traceback (most recent call last):
      File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py", line 39, in <module>
        BeforeStartHook().execute()
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 257, in execute
        method(env)
      File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py", line 28, in hook
        import params
      File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py", line 316, in <module>
        immutable_paths = get_not_managed_resources(),
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py", line 38, in get_not_managed_resources
        managed_hdfs_resource_property_list = filter(None, [property.strip() for property in managed_hdfs_resource_property_names.split(',')])
      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 'managed_hdfs_resource_property_names' was not found in configurations dictionary!
    Error: Error: Unable to run the custom hook script ['/usr/bin/python', '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py', 'START', '/var/lib/ambari-agent/data/command-603.json', '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START', '/var/lib/ambari-agent/data/structured-out-603.json', 'INFO', '/var/lib/ambari-agent/tmp']
    





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)