Bug 1448457

Summary: docker-cleanup.timer triggers docker to start if it's not currently running
Product: Red Hat Enterprise Linux 7 Reporter: Scott Dodson <sdodson>
Component: dockerAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: amurdaca, jhonce, lsm5, lsu
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: docker-1.12.6-22.git62520c0.el7_3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-26 14:52:18 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:
Attachments:
Description Flags
fix jhonce: review? (lsm5)

Description Scott Dodson 2017-05-05 13:04:47 UTC 
Description of problem:

If docker has been stopped then docker-cleanup.timer will trigger docker to start unexpectedly.

Version-Release number of selected component (if applicable):
1.12.6-16

How reproducible:
100%

Steps to Reproduce:
1. yum install docker
2. systemctl start docker
3. systemctl stop docker
4. Wait until within 1 minute of the top of the hour
5. docker-cleanup.timer fires and docker is started


Actual results:
docker-cleanup.timer starts docker if it's not started

Expected results:
docker-cleanup.timer shouldn't start docker if it's not currently running

Additional info:
Comment 3 Jhon Honce 2017-05-08 17:37:07 UTC 
Created attachment 1277138 [details]
fix
Comment 4 Scott Dodson 2017-05-09 14:51:51 UTC 
Did a quick test by replicating the changes locally, seems to fix the issue.
Comment 7 Luwen Su 2017-05-15 09:43:45 UTC 
The docker service doesn't start again that trigger by docker-cleanup.timer in docker-1.12.6-26.git62520c0.el7.x86_64, move to verified.
Comment 9 errata-xmlrpc 2017-05-26 14:52:18 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://access.redhat.com/errata/RHBA-2017:1325