Bug 1319783
| Summary: | [docker] Use Restart=on-abnormal instead of Restart=on-failure | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vivek Goyal <vgoyal> |
| Component: | docker | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | aos-bugs, bleanhar, cevich, chaoyang, dmcphers, dwalsh, jhonce, jialiu, jokerman, lsm5, lsu, misalunk, mmccomas, vgoyal |
| Target Milestone: | rc | Keywords: | Extras, UpcomingRelease |
| Target Release: | 7.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1276346 | Environment: | |
| Last Closed: | 2016-05-12 15:17:28 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: | |||
| Bug Depends On: | 1276346 | ||
| Bug Blocks: | 1303656 | ||
|
Comment 3
Luwen Su
2016-05-01 11:12:01 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 |