Bug 1231305

Summary: docker-registry systemd script uses non-existing option for gunicorn
Product: [Fedora] Fedora Reporter: Thorsten Scherf <tscherf>
Component: docker-registryAssignee: Marek Goldmann <mgoldman>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 22CC: admiller, lsm5, mgoldman, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 11:37:03 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 Thorsten Scherf 2015-06-12 15:52:19 UTC 
Description of problem:

/usr/lib/systemd/system/docker-registry.service contains this line to start the service:

/usr/bin/gunicorn --access-logfile - --debug --max-requests 100 --graceful-timeout 3600 -t 3600 -k gevent -b  localhost:5000 -w 2 docker_registry.wsgi:application

The gunicorn app doesn't know about an option "debug", which results in an error when you start the service with "systemctl start docker-registry":

Jun 12 17:39:16 kubernetes.example.com systemd[1]: docker-registry.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jun 12 17:39:16 kubernetes.example.com systemd[1]: Unit docker-registry.service entered failed state.
Jun 12 17:39:16 kubernetes.example.com systemd[1]: docker-registry.service failed.

Removing the debug option from the systemd script fixes the issue.


Version-Release number of selected component (if applicable):
docker-registry-0.9.1-1.fc22.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Tim Waugh 2015-06-30 11:37:03 UTC 

*** This bug has been marked as a duplicate of bug 1207308 ***