Bug 1334150

Summary: gssproxy daemon cannot start if the user apache does not exist
Product: [Fedora] Fedora Reporter: Yu Watanabe <watanabe.yu>
Component: gssproxyAssignee: Robbie Harwood <rharwood>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: gdeschner, rharwood, ssorce, watanabe.yu
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: gssproxy-0.5.0-4.fc24 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-14 23:29:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yu Watanabe 2016-05-09 03:11:37 UTC
Description of problem:

If the user apache does not exist, then gssproxy daemon fails to start with the following error messages:
=================
May 09 11:51:08 systemd[1]: Starting GSSAPI Proxy Daemon...
May 09 11:51:08 gssproxy[4538]: Option 'euid' is missing from [service/HTTP].
May 09 11:51:08 gssproxy[4538]: Error reading configuration 22: Invalid argument
May 09 11:51:08 systemd[1]: gssproxy.service: Control process exited, code=exited status=1
May 09 11:51:08 systemd[1]: Failed to start GSSAPI Proxy Daemon.
May 09 11:51:08 systemd[1]: gssproxy.service: Unit entered failed state.
May 09 11:51:08 systemd[1]: gssproxy.service: Failed with result 'exit-code'.
=================

Version-Release number of selected component (if applicable):

gssproxy-0.5.0-3.fc24.x86_64
gssproxy-0.5.0-3.fc25.x86_64

How reproducible:

always.

Steps to Reproduce:
1. Install system without httpd
2. Install gssproxy
3. Start gssproxy service

Actual results:

The unit gssproxy.service entered failed state.

Expected results:

The unit gssproxy.service starts successfully.

Additional info:

In /etc/gssproxy/80-httpd.conf, 'euid = apache' is specified. However, the user apache does not exist if httpd.rpm has not been installed.
I think 80-httpd.conf should be disabled by default, e.g., by moving it to /usr/share/doc/gssproxy/examples or packaging it in gssproxy-httpd sub-package.

Comment 1 Fedora Update System 2016-05-09 21:52:53 UTC
gssproxy-0.5.0-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c68f632054

Comment 2 Fedora Update System 2016-05-10 20:28:58 UTC
gssproxy-0.5.0-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c68f632054

Comment 3 Fedora Update System 2016-05-14 23:28:49 UTC
gssproxy-0.5.0-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.