[jira] [Commented] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

2016-10-06 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-18549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553043#comment-15553043
 ] 

Hudson commented on AMBARI-18549:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5771 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5771/])
AMBARI-18549. oozie server start fails post upgrade to Ambari 2.4.1 (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=49c9660c39c379b5568f9cff2d0fad44bde03222])
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py


> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> 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 
> OozieServer().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/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 164, in oozie_service
> user = params.oozie_user)
>   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 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



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

[jira] [Commented] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

2016-10-06 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-18549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552917#comment-15552917
 ] 

Hudson commented on AMBARI-18549:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #122 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/122/])
AMBARI-18549. oozie server start fails post upgrade to Ambari 2.4.1 (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8678f46d945c20ad9555a50bf2bf68a0edac3c6a])
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py


> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> 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 
> OozieServer().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/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 164, in oozie_service
> user = params.oozie_user)
>   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 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



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

[jira] [Commented] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

2016-10-06 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-18549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552440#comment-15552440
 ] 

Hadoop QA commented on AMBARI-18549:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12831985/AMBARI-18549.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8824//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8824//console

This message is automatically generated.

> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> 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 
> OozieServer().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/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 164, in oozie_service
> user = params.oozie_user)
>   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 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



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