Bug 1430613

Summary: openshift-excluder should be enabled after install ocp
Product: OpenShift Container Platform Reporter: liujia <jiajliu>
Component: InstallerAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: liujia <jiajliu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
The installer now installs and configures the atomic-openshift-excluder and atomic-openshift-docker excluder packages as part of the installation process. The install and upgrade playbooks also disable the excluders when necessary. By installing the excluders by default users are protected from inadvertent upgrades when not running the install and upgrade playbooks.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-12 19:03:18 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 liujia 2017-03-09 06:43:03 UTC
Description of problem:
Trigger an rpm install against fresh hosts(without excluders). Openshift-excluder are installed during ocp installation, but it is not enabled after installation completed.

# rpm -qa | grep excluder
atomic-openshift-excluder-3.5.0.48-1.git.0.75d2644.el7.noarch
# cat /etc/yum.conf | grep exclude
exclude=


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.5.28-1.git.0.103513e.el7.noarch

How reproducible:
always

Steps to Reproduce:
1.Install OCP3.5 on fresh hosts
2.
3.

Actual results:
openshift-excluder are not enabled after install ocp.

Expected results:
openshift-excluder should be enabled.

Additional info:

Comment 1 Jan Chaloupka 2017-03-09 15:38:33 UTC
Actually, the openshift excluder was never re-enabled. It is disabled since we need to detect openshift version to install. With the excluder on it is not possible.

Upstream PR: https://github.com/openshift/openshift-ansible/pull/3610

Comment 2 Jan Chaloupka 2017-03-09 15:39:12 UTC
*** Bug 1430612 has been marked as a duplicate of this bug. ***

Comment 3 liujia 2017-03-10 02:32:24 UTC
@Jan

It is different from bug1430612. Openshift-excluder should works in different way with docker-excluder. 

As for openshift-excluder, it should be disable during installation, but should be restored to be enabled after installation.

As for docker-excluder, it should be enabled during installation, and always enabled after installation.

Comment 4 Jan Chaloupka 2017-03-10 14:18:37 UTC
Solving bug1430612 as a separate issue. This issues gets resolved once https://github.com/openshift/openshift-ansible/pull/3610 is merged.

Comment 5 Jan Chaloupka 2017-03-11 22:17:36 UTC
Merged upstrema.

Comment 7 liujia 2017-03-14 03:04:18 UTC
Version:
atomic-openshift-utils-3.5.32-1.git.0.42cf266.el7.noarch

Steps:
1. Rpm install OCP3.5 on fresh hosts

Result:
Openshift-excluder is installed and enabled after installation.


openshift-119.x.x.x | SUCCESS | rc=0 >>
atomic-openshift-excluder-3.5.0.51-1.git.0.d07622a.el7.noarch
atomic-openshift-docker-excluder-3.5.0.51-1.git.0.d07622a.el7.noarch

openshift-118.x.x.x | SUCCESS | rc=0 >>
atomic-openshift-excluder-3.5.0.51-1.git.0.d07622a.el7.noarch
atomic-openshift-docker-excluder-3.5.0.51-1.git.0.d07622a.el7.noarch


openshift-119.x.x.x | SUCCESS | rc=0 >>
exclude -- All packages excluded

openshift-118.x.x.x | SUCCESS | rc=0 >>
exclude -- All packages excluded

Comment 9 errata-xmlrpc 2017-04-12 19:03:18 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:0903