[ https://issues.apache.org/jira/browse/AMBARI-16906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303749#comment-15303749 ]
Hadoop QA commented on AMBARI-16906: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806442/AMBARI-16906.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {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:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7008//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7008//console This message is automatically generated. > Express upgrade: Oozie failed to start when user name and group are > none-default values > --------------------------------------------------------------------------------------- > > Key: AMBARI-16906 > URL: https://issues.apache.org/jira/browse/AMBARI-16906 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: trunk > Reporter: Di Li > Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-16906.patch > > > oozie_server_upgrade.py has hardcoded user name to oozie and group to hadoop. > Both values should have been pulled from params.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)