Bug 1403696
| Summary: | [3.3] excluder did not add expexcted excluded packages into yum.conf | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> | |
| Component: | Cluster Version Operator | Assignee: | Scott Dodson <sdodson> | |
| Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.3.1 | CC: | aos-bugs, bleanhar, jokerman, mmccomas, tdawson | |
| Target Milestone: | --- | Keywords: | Reopened | |
| Target Release: | 3.3.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
The atomic-openshift-excluder and atomic-openshift-docker-excluder packages did not properly configure yum to exclude the relevant packages. The excluder scripts have been updated to ensure the proper yum configuration is modified ensuring that the appropriate packages are excluded from yum operations.
|
Story Points: | --- | |
| Clone Of: | 1402693 | |||
| : | 1404106 (view as bug list) | Environment: | ||
| Last Closed: | 2017-01-26 20:43:00 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: | ||||
| Bug Depends On: | 1402693 | |||
| Bug Blocks: | 1404106 | |||
|
Comment 1
liujia
2016-12-12 08:47:20 UTC
Fixed in v3.3.1.8 Version: atomic-openshift-excluder-3.3.1.9-1.git.0.a7f5265.el7.noarch atomic-openshift-docker-excluder-3.3.1.9-1.git.0.a7f5265.el7.noarch Steps: 1. Install OCP3.3 on rhel hosts. 2. Install atomic-openshift-excluder and Result: It will run "atomic-openshift-excluder exclude" and "atomic-openshift-docker-excluder exclude" by default and all expected excluded packages have been added into yum.conf correctly. The bug has been fixed in OCP3.3 now. 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:0199 |