Bug 1395761 - The docker-selinux wasn't upgrade by upgrade playbook [NEEDINFO]
Summary: The docker-selinux wasn't upgrade by upgrade playbook
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 15:45 UTC by Anping Li
Modified: 2019-03-06 01:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-30 15:13:28 UTC
Target Upstream Version:
anli: needinfo? (lsm5)


Attachments (Terms of Use)

Description Anping Li 2016-11-16 15:45:44 UTC
Description of problem:
There are still docker-selinux-1.10.3-57.el7.x86_64 after upgrade to docker-1.12.3. The selinux should be upgraded by upgrade playbooks


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


How reproducible:
always

Steps to Reproduce:
1. install ocp 3.3 with docker-1.10.3
2. upgrade to ocp 3.4
3. check the docker related packages after upgrade


Actual results:
[root@qe-anli-upg-node-container-registry-router-1 ~]# rpm -qa|grep docker
docker-rhel-push-plugin-1.12.3-4.el7.x86_64
docker-common-1.12.3-4.el7.x86_64
docker-1.12.3-4.el7.x86_64
docker-selinux-1.10.3-57.el7.x86_64


Expected results:
docker-selinux-1.10.3-57.el7.x86_64 was replaced by container-selinux-1.12.3-4.el7.x86_64

Additional info:

Comment 1 Devan Goodwin 2016-11-17 12:30:27 UTC
Re-assigning to Docker component to confirm if this is a problem or not, and if so I suspect it's likely best handled in docker's rpm deps.

Comment 2 Daniel Walsh 2016-11-17 22:18:20 UTC
This should have brought in container-selinux, but since we pulled out docker-1.12 it probably can be pushed back to next release.

Comment 3 Anping Li 2016-11-18 01:22:56 UTC
Must we upgrade to container-selinux-1.12.3-4.el7.x86_64?  Is there any issue if docker-1.12 work with docker-selinux-1.10.3?

Comment 5 Anping Li 2017-02-22 07:11:46 UTC
Update the new status:
when I upgraded 1.10.3 to docker-1.12.5. The container-selinux-1.12.5 will be installed and docker-selinux-1.10.3 was kept. 
I am not sure if we need to remove the package docker-selinux-1.10.3. it seems like a duplicate packages with container-selinux-1.12.5 .

Comment 6 Daniel Walsh 2017-06-30 15:13:28 UTC
I think this is fixed in the current release.


Note You need to log in before you can comment on or make changes to this bug.