Bug 1366803
| Summary: | [extras-rhel-7.3.0] rhel-push-plugin left running after rpm -e docker-* | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Qian Cai <qcai> |
| Component: | docker | Assignee: | Frantisek Kluknavsky <fkluknav> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.2 | CC: | atomic-bugs, dwalsh, fkluknav, lsm5, lsu |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1366802 | Environment: | |
| Last Closed: | 2017-08-02 00:11:21 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: | 1366802 | ||
| Bug Blocks: | |||
|
Description
Qian Cai
2016-08-12 21:22:37 UTC
Why would removing docker do anything to docker-push-plugin, it could potentially be used by docker-latest? I don't think this is a bug. The issue is that if people removed rhel-push-plugin rpm, they probably expect a postrm trigger to stop the running rhel-push-plugin processe. Ah, OK, That is not how I read the bug report. Lokesh can you make sure the pre(uninstall) kills the service. (In reply to Daniel Walsh from comment #4) > Ah, OK, That is not how I read the bug report. > > Lokesh can you make sure the pre(uninstall) kills the service. will do. This fix can go into 7.3 correct? Lokesh, are you going to use this same BZ to fix a similar issue with docker-lvm-plugin and docker-novolume-plugin as well or do you want to open separate BZs for those? Can we move this to the modified state? Franticek could you check to see if we still have this issue? With docker-1.12.6-34.gitf55a118.el7.x86_64 (latest 7.3 currently): # ps axu|grep docker root 1677 0.0 0.4 31228 4700 ? Ssl 08:58 0:00 /usr/libexec/docker/rhel-push-plugin root 1699 0.8 2.1 563024 22240 ? Ssl 08:58 0:00 /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --authorization-plugin=rhel-push-plugin --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --selinux-enabled --log-driver=journald --signature-verification=false --add-registry registry.access.redhat.com root 1704 0.0 0.6 262972 6924 ? Ssl 08:58 0:00 /usr/bin/docker-containerd-current -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim docker-containerd-shim --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --runtime docker-runc --runtime-args --systemd-cgroup=true root 1808 0.0 0.0 112660 992 pts/0 R+ 08:58 0:00 grep --color=auto docker # rpm -qa|grep docker|xargs yum erase # ps axu|grep docker root 1944 0.0 0.0 112660 992 pts/0 S+ 09:02 0:00 grep --color=auto docker Seems working correctly # rpm -qa|grep docker|xargs yum erase -y Removed: docker.x86_64 2:1.12.6-48.git0fdc778.el7 docker-client.x86_64 2:1.12.6-48.git0fdc778.el7 docker-common.x86_64 2:1.12.6-48.git0fdc778.el7 docker-lvm-plugin.x86_64 2:1.12.6-48.git0fdc778.el7 docker-novolume-plugin.x86_64 2:1.12.6-48.git0fdc778.el7 docker-rhel-push-plugin.x86_64 2:1.12.6-48.git0fdc778.el7 docker-v1.10-migrator.x86_64 2:1.12.6-48.git0fdc778.el7 python-docker-py.noarch 0:1.10.6-1.el7 python-docker-pycreds.noarch 0:1.10.6-1.el7 Dependency Removed: atomic.x86_64 1:1.18.1-3.1.git0705b1b.el7 Complete! # ps axu|grep docker root 2461 0.0 0.0 112664 976 pts/0 S+ 00:16 0:00 grep --color=auto docker 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:2344 |