Pankaj Singh created AMBARI-17316:
-------------------------------------
Summary: [Zeppelin][Ambari] Service restart fails if one modifies
the parameter "zeppelin_log_dir"
Key: AMBARI-17316
URL: https://issues.apache.org/jira/browse/AMBARI-17316
Project: Ambari
Issue Type: Bug
Components: ambari-server, ambari-web
Affects Versions: ambari-2.4.0
Environment: Centos6
Reporter: Pankaj Singh
Priority: Critical
Fix For: ambari-2.4.0
There are 2 issues
# if a user modifies the "zeppelin_log_dir" parameter to a directory which is
not present e.g. from /var/log to /tmp/log , save the configuration and
restarts the service ,"Restart Zeppelin Notebook" Operation fails with error
{code}
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 189, in action_create
raise Fail("Applying %s failed, parent directory %s doesn't exist" %
(self.resource, dirname))
resource_management.core.exceptions.Fail: Applying
Directory['/tmp/log/zeppelin'] failed, parent directory /tmp/log doesn't exist
{code}
This is not sync with other services, For eg if one modifies the log directory
for Hive Service from /var/log/hive to /tmp/log/hive. and restarts the
service,. The Hive Service restarts successfully
# The second issue is even if the service restart fails the service status
shown is GREEN and not RED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
