[
https://issues.apache.org/jira/browse/AMBARI-14526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609599#comment-15609599
]
Hadoop QA commented on AMBARI-14526:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12830480/AMBARI-14526.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9014//console
This message is automatically generated.
> CentOS 7.2/RHEL 7.2 ambari-server systemd script is broken
> ----------------------------------------------------------
>
> Key: AMBARI-14526
> URL: https://issues.apache.org/jira/browse/AMBARI-14526
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Greg Hill
> Assignee: Henning Kropp
> Fix For: trunk
>
> Attachments: AMBARI-14526.patch
>
>
> systemd was updated in RHEL 7.2 and thus also in CentOS 7.2. This update
> breaks compatibility with how ambari-server starts up. There is a simple
> fix, just create the file /usr/lib/systemd/system/ambari-server.service with
> these contents:
> {noformat}
> [Unit]
> Description=ambari-server service
> After=xe-linux-distribution.service
> [Service]
> Type=forking
> ExecStart=/usr/sbin/ambari-server start
> ExecStop=/usr/sbin/ambari-server stop
> [Install]
> WantedBy=multi-user.target
> {noformat}
> There's probably a better way to work with systemd in a more systemd-ish way,
> but this restores compatibility for now with minimal effort. We should
> update the RPM to install this file if the system is managed by systemd.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
