Bug 1231305 - docker-registry systemd script uses non-existing option for gunicorn
Summary: docker-registry systemd script uses non-existing option for gunicorn
Keywords:
Status: CLOSED DUPLICATE of bug 1207308
Alias: None
Product: Fedora
Classification: Fedora
Component: docker-registry
Version: 22
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Marek Goldmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-12 15:52 UTC by Thorsten Scherf
Modified: 2015-06-30 11:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 11:37:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.