RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1319783 - [docker] Use Restart=on-abnormal instead of Restart=on-failure
Summary: [docker] Use Restart=on-abnormal instead of Restart=on-failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 7.2
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On: 1276346
Blocks: docker-1.10
TreeView+ depends on / blocked
 
Reported: 2016-03-21 14:09 UTC by Vivek Goyal
Modified: 2020-09-21 07:32 UTC (History)
14 users (show)

Fixed In Version: docker-1.9.1-38.el7
Doc Type: Bug Fix
Doc Text:
Cause: Previously, the Docker unit file had Restart=on-failure. Consequence: This would force the docker daemon to restart even in cases where it couldn't be started because of configuration or other issues and this would force a restart of docker-storage-setup in a loop which is completely unnecessary and real error messages are also lost due to so many restarts. Fix: Restart=on-failure has been replaced with Restart=on-abnormal in the docker unit file Result: Docker daemon will not automatically restart if it fails with an unclean exit code.
Clone Of: 1276346
Environment:
Last Closed: 2016-05-12 15:17:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1034 0 normal SHIPPED_LIVE Moderate: docker security, bug fix, and enhancement update 2016-05-12 19:15:01 UTC

Comment 3 Luwen Su 2016-05-01 11:12:01 UTC 
In docker-1.9.1-38.el7.x86_64,
catch Restart=on-abnormal in /usr/lib/systemd/system/docker.service
move to verified
Comment 5 errata-xmlrpc 2016-05-12 15:17:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-1034.html
Note You need to log in before you can comment on or make changes to this bug.