Bug 1403655 - yum install atomic-openshift-docker-excluder failed after atomic-openshift-excluder was installed
Summary: yum install atomic-openshift-docker-excluder failed after atomic-openshift-ex...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Troy Dawson
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 06:14 UTC by liujia
Modified: 2017-03-23 13:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2016-12-14 15:39:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 17:23:26 UTC

Description liujia 2016-12-12 06:14:57 UTC
Description of problem:
After install atomic-openshift-excluder, it will exclude the following install of atomic-docker-excluder trough yum. Because atomic-openshift-excluder's postinstall script will run "atomic-openshift-excluder exclude" by default to add "atomic-openshift-docker-excluder" into yum.conf, which result that docker-excluder can not be installed through yum.

Version-Release number of selected component (if applicable):
atomic-openshift-excluder-3.4.0.34-1.git.0.87d9d8d.el7.noarch
atomic-openshift-docker-excluder-3.4.0.34-1.git.0.87d9d8d.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. install ocp3.4 on rhel hosts.
2. install atomic-openshift-excluder. 
3. yum install atomic-openshift-docker-excluder.

Actual results:
Docker-excluder will not be installed.

Expected results:
It should not run exclude command by default after install excluder.

Additional info:
1.User can run "atomic-openshift-excluder unexclude" after install openshift-excluder to workaround this issue.
2.User also can download atomic-openshift-docker-excluder package and rpm install it to workaround this issue.

Comment 1 Troy Dawson 2016-12-12 16:58:43 UTC
It has been determined that Upstream (Origin) would need the excluders excluded (both origin-excluder and origin-docker-excluder), Downstream (atomic-openshift) would not need them excluded.
This is because Downstream (OpenShift Container Platform - formerly OSE) has different versions separated into different channels.  Thus with OCP 3.3, you would not accidentally update to atomic-openshift-docker-excluder-3.4, because 3.4 is in a different channel.

Because of this decision, we will not exclude the excluders in atomic-openshift-excluder.

A fix for this will be coming soon.

Comment 2 Troy Dawson 2016-12-12 19:30:51 UTC
Fixed in this pull request.
https://github.com/openshift/ose/pull/506

Comment 4 liujia 2016-12-14 02:42:24 UTC
Version:
atomic-openshift-excluder-3.4.0.36-1.git.0.ca20a16.el7.noarch

Steps:
1. install ocp3.4 on rhel hosts.
2. install atomic-openshift-excluder. 
3. yum install atomic-openshift-docker-excluder.

Result:
For step2, excluders has been removed from package_list.
PACKAGE_LIST="atomic-openshift atomic-openshift-clients atomic-openshift-clients-redistributable atomic-openshift-dockerregistry atomic-openshift-master atomic-openshift-node atomic-openshift-pod atomic-openshift-recycle atomic-openshift-sdn-ovs atomic-openshift-tests tuned-profiles-atomic-openshift-node"

# cat /etc/yum.conf | grep exclude
exclude= tuned-profiles-atomic-openshift-node  atomic-openshift-tests  atomic-openshift-sdn-ovs  atomic-openshift-recycle  atomic-openshift-pod  atomic-openshift-node  atomic-openshift-master  atomic-openshift-dockerregistry  atomic-openshift-clients-redistributable  atomic-openshift-clients  atomic-openshift

For step3,atomic-openshift-docker-excluder can be installed successfully.

Comment 5 Troy Dawson 2016-12-14 15:39:27 UTC
This was never released, and no customers saw it.  Closing bug now that it's been fixed and verified.


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