Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1395761

Summary: The docker-selinux wasn't upgrade by upgrade playbook
Product: Red Hat Enterprise Linux 7 Reporter: Anping Li <anli>
Component: dockerAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED CURRENTRELEASE QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: amurdaca, aos-bugs, dgoodwin, dwalsh, jokerman, lsm5, mmccomas
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-30 15:13:28 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:

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.