Bug 1437784

Summary: update docker 1.12.5 to 1.12.6 with paused containers is not finished/hangs
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Spanko <jspanko>
Component: dockerAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: amurdaca, dornelas, dwalsh, lsm5, lsu, uobergfe
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: docker-1.12.6-19.git92b10e4.el7_3 Doc Type: Bug Fix
Doc Text:
Cause: RHEL7 currently can not support the live-restore containers, there are issues in the kernel that prevent this from working. Accidently the previous update turned on live-restore. Consequence: This had the potential of causing docker daemon to hang and not function properly. Fix: Remove live-restore from the docker daemon configuration Result: The daemon works properly.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-26 14:51:45 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: 1186913, 1441768    

Description Jaroslav Spanko 2017-03-31 07:49:26 UTC
Description of problem:
Update of docker hangs on cleanup message.
# rpm docker 
docker-1.12.5-14.el7.x86_64                         Mon Jan 23 21:33:05 2017

# yum update docker 
Running transaction
Updating   : 2:docker-common-1.12.6-11.el7.x86_64                       1/11                                                      
warning: /etc/sysconfig/docker created as /etc/sysconfig/docker.rpmnew
Updating   : 2:docker-client-1.12.6-11.el7.x86_64                       2/11                                                                            
Updating   : 2:docker-rhel-push-plugin-1.12.6-11.el7.x86_64             3/11                                                                   
Installing : 2:container-selinux-2.9-4.el7.noarch                       4/11                                                                             
Updating   : 2:docker-1.12.6-11.el7.x86_64                              5/11                                                                              
Erasing    : docker-selinux-1.10.3-46.el7.10.x86_64                     6/11                                                                     
Cleanup    : 2:docker-1.12.5-14.el7.x86_64                              7/11                                                           
Hangs here

Needs to be kill, docker packages were not removed:
docker-1.12.5-14.el7.x86_64                           Mon Jan 23 21:33:05 2017
docker-1.12.6-11.el7.x86_64                           Mon Mar 27 16:49:42 2017

This cause live restore option in daemon.json:
{
            "live-restore": true

}
Version-Release number of selected component (if applicable):
RHEL 7.x
docker-1.12.5-14.el7.x86_64                          


How reproducible:
100%

Steps to Reproduce:
1. yum update docker

Actual results:
Yum have to be killed to proceed docker update

Expected results:
Update successful

Additional info:
In case of "live-restore": true update is not possible.
In Fedora update works

Thanks

Comment 2 Jaroslav Spanko 2017-03-31 08:02:31 UTC
Sorry i forgot to add
Update is not possible only in case there are paused containers
CONTAINER ID        IMAGE               COMMAND              CREATED             STATUS                   PORTS               NAMES
19af1d73e712        httpd               "httpd-foreground"   34 seconds ago      Up 32 seconds (Paused)   80/tcp              test1

Comment 5 Daniel Walsh 2017-04-12 15:29:12 UTC
We could add a preinstall with something like

docker stop $(docker ps -a -q)

Until we move to rhel7.4

Comment 10 errata-xmlrpc 2017-05-26 14:51:45 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