RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1366803 - [extras-rhel-7.3.0] rhel-push-plugin left running after rpm -e docker-*
Summary: [extras-rhel-7.3.0] rhel-push-plugin left running after rpm -e docker-*
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Frantisek Kluknavsky
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On: 1366802
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-12 21:22 UTC by Qian Cai
Modified: 2019-03-06 00:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1366802
Environment:
Last Closed: 2017-08-02 00:11:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2344 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2017-08-08 22:51:38 UTC

Description Qian Cai 2016-08-12 21:22:37 UTC 
+++ This bug was initially created as a clone of Bug #1366802 +++

Description of problem:
# rpm -qa | grep docker | xargs rpm -e
warning: /etc/sysconfig/docker-latest-storage-setup saved as /etc/sysconfig/docker-latest-storage-setup.rpmsave
warning: /etc/sysconfig/docker-latest-storage saved as /etc/sysconfig/docker-latest-storage.rpmsave

# # ps aux | grep docker
root      9865  0.0  0.1  45496  6156 ?        Ssl  Aug11   0:09 /usr/libexec/docker/rhel-push-plugin
root     14948  0.0  0.1 277012  6804 ?        Ssl  17:11   0:00 

Version-Release number of selected component (if applicable):
# rpm -qa | grep docker
docker-common-1.10.3-46.el7.10.x86_64
docker-rhel-push-plugin-1.10.3-46.el7.10.x86_64
docker-selinux-1.10.3-46.el7.10.x86_64
docker-latest-1.12.0-4.el7.x86_64

How reproducible:
always
Comment 2 Daniel Walsh 2016-08-15 12:48:44 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.
Comment 3 Qian Cai 2016-08-15 13:01:25 UTC 
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.
Comment 4 Daniel Walsh 2016-08-15 13:18:14 UTC 
Ah, OK,  That is not how I read the bug report.

Lokesh can you make sure the pre(uninstall) kills the service.
Comment 5 Lokesh Mandvekar 2016-08-15 15:07:51 UTC 
(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?
Comment 6 Qian Cai 2016-08-15 15:37:51 UTC 
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?
Comment 7 Daniel Walsh 2016-08-19 21:13:16 UTC 
Can we move this to the modified state?
Comment 11 Daniel Walsh 2017-06-30 16:02:47 UTC 
Franticek could you check to see if we still have this issue?
Comment 12 Frantisek Kluknavsky 2017-07-12 13:15:10 UTC 
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
Comment 14 Luwen Su 2017-07-22 16:16:57 UTC 
# 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
Comment 16 errata-xmlrpc 2017-08-02 00:11:21 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:2344
Note You need to log in before you can comment on or make changes to this bug.