ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16906) Express upgrade: Oozie failed to start when user name and group are none-default values
Date Fri, 27 May 2016 21:57:12 GMT

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

Hudson commented on AMBARI-16906:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4944 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4944/])
AMBARI-16906 Express upgrade: Oozie failed to start when user name and (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a94a03f55605294e7aed061b9673c87c262d16f6])
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py


> 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)

Mime
View raw message