Bug 1276346
Summary: | Docker Service Crash | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Miheer Salunke <misalunk> | |
Component: | docker | Assignee: | Lokesh Mandvekar <lsm5> | |
Status: | CLOSED ERRATA | QA Contact: | Chao Yang <chaoyang> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 7.2 | CC: | aos-bugs, bleanhar, cevich, dmcphers, dwalsh, jialiu, jokerman, lsm5, mmccomas, tpoitras, vgoyal | |
Target Milestone: | rc | Keywords: | Extras, UpcomingRelease | |
Target Release: | 7.2 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | docker-1.8.2-10.el7 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, if the Docker service crashed on a node, it did not automatically restart. As a result, you would need to log in to the master itself and manually start the service in order to have the environment running properly. Now, this has been fixed, and the Docker service is automatically restarted after a failure.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1319783 (view as bug list) | Environment: | ||
Last Closed: | 2015-12-08 15:36: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: | ||||
Bug Blocks: | 1319783 |
Comment 9
errata-xmlrpc
2015-12-08 15:36:28 UTC
I am reopening this bug. Instead of Restart=on-failure, we should consider using Restart=on-abnormal. Reason being that otherwise we try to restart docker multiple times even when docker can't start and has configuration issues. And as a result, it forces restart of docekr-storage-setup and all I see in logs is following. systemd[1]: docker.service failed. systemd[1]: start request repeated too quickly for docker.service systemd[1]: Failed to start Docker Application Container Engine. |