Bug 1593209
| Summary: | The openshift exclude packages need update | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
| Component: | Installer | Assignee: | Russell Teague <rteague> |
| Installer sub component: | openshift-ansible | QA Contact: | liujia <jiajliu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, ckoep, cshereme, jiajliu, jialiu, jokerman, mmccomas, rteague, vjaypurk |
| Version: | 3.10.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Packages required for openshift are updated in the openshift excluder.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-20 10:11:10 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
2018-06-20 09:45:57 UTC
I'm not sure I understand the problem you're describing? Are you saying that during a 3.9 to 3.10 upgrade you don't get any exclude set? The value you've posted looks fine to me. The docker excluders exclude specific versions. The atomic-openshift ones do no. In v3.10, atomic-openshift-sdn-ovs and atomic-openshift-master does not exist at all, but they are still in the excluded list. Instead, atomic-openshift-hyperkube was not added in the excluded list. Need to add hyperkube to the excludes configuration in origin.spec and remove items that are no longer relevant. Commits pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/dd5bf4cf9246640e41eda50f67e7949c889ca410 Bug 1593209 - Update OpenShift Excluder * Adds -hyperkube * Removes -sdn-ovs Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1593209 https://github.com/openshift/origin/commit/d7c2dc7a9f2d9164eee3753a55f5ede7257ef1a2 Merge pull request #20059 from mtnbikenc/fix-1593209 Bug 1593209 - Update OpenShift Excluder release-3.10: https://github.com/openshift/origin/pull/20081 In build v3.10.7-1. Version:openshift-ansible-3.10.9-1.git.240.1c86105.el7.noarch.rpm Fresh install v3.10 ocp. # cat /etc/yum.conf |grep exclude exclude= atomic-openshift-tests atomic-openshift-hyperkube atomic-openshift-recycle atomic-openshift-pod atomic-openshift-node atomic-openshift-master atomic-openshift-clients-redistributable atomic-openshift-clients atomic-openshift docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* Upgrade v3.9 to v3.10. before: # cat /etc/yum.conf |grep exclude exclude= atomic-openshift-tests atomic-openshift-sdn-ovs atomic-openshift-recycle atomic-openshift-pod atomic-openshift-node atomic-openshift-master atomic-openshift-clients-redistributable atomic-openshift-clients atomic-openshift docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* after: # cat /etc/yum.conf |grep exclude exclude= atomic-openshift-tests atomic-openshift-hyperkube atomic-openshift-recycle atomic-openshift-pod atomic-openshift-node atomic-openshift-master atomic-openshift-clients-redistributable atomic-openshift-clients atomic-openshift docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* Adds -hyperkube,Removes -sdn-ovs, but unused atomic-openshift-master&atomic-openshift-pod still existed in yum.conf. @Russell Teague Could u have a confirm if we need remove it from the list? We will consider removing items -master and -pod in a future udpate, however, there is no consequence of having them present in the excluders for now. The exclude line needs to continue to contain the atomic-openshift-sdn-ovs package, because this package still exists in the 3.10 repository and has a dependency of packages that ARE included in the exclude line. This will ALWAYS break yum updates if the package is installed in a 3.10 environment. Customer is seeing:
Error: Package: atomic-openshift-sdn-ovs-3.10.72-1.git.0.3cb2fdc.el7.x86_64 (rhel-7-server-ose-3.10-rpms)
Requires: atomic-openshift-node = 3.10.72-1.git.0.3cb2fdc.el7
Installed: atomic-openshift-node-3.10.45-1.git.0.3b98bf6.el7.x86_64 (@rhel-7-server-ose-3.10-rpms)
atomic-openshift-node = 3.10.45-1.git.0.3b98bf6.el7
The package atomic-openshift-node, version 3.10.72-1.git.0.3cb2fdc.el7, does not appear in the required version in the output of "yum list available." The message appears whether or not the openshift packages are excluded via "atomic-openshift-excluder".
The cluster was set up using the AWS Quickstart. The list of repositories is:
repo id repo name status
epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 12,737+1
rh-gluster-3-client-for-rhel-7-server-rpms/7Server/x86_64 Red Hat Storage Native Client for RHEL 7 (RPMs) 218
rhel-7-fast-datapath-rpms/7Server/x86_64 Red Hat Enterprise Linux Fast Datapath (RHEL 7 Server) (RPMs) 139
rhel-7-server-ansible-2.4-rpms/x86_64 Red Hat Ansible Engine 2.4 RPMs for Red Hat Enterprise Linux 7 Server 23
rhel-7-server-extras-rpms/x86_64 Red Hat Enterprise Linux 7 Server - Extras (RPMs) 1,022
rhel-7-server-ose-3.10-rpms/x86_64 Red Hat OpenShift Container Platform 3.10 (RPMs) 629+40
rhel-7-server-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server (RPMs) 23,342
rhui-REGION-client-config-server-7/x86_64 Red Hat Update Infrastructure 2.0 Client Configuration Server 7 1
rhui-REGION-rhel-server-releases/7Server/x86_64 Red Hat Enterprise Linux Server 7 (RPMs) 23,342
rhui-REGION-rhel-server-rh-common/7Server/x86_64 Red Hat Enterprise Linux Server 7 RH Common (RPMs) 235
I can reproduce in my 3.10 env by trying to install the package (which does exist in the 3.10 repos):
[root@ignotus ~]# yum install atomic-openshift-sdn-ovs
Loaded plugins: product-id, search-disabled-repos, subscription-manager
rhel-7-fast-datapath-rpms | 2.3 kB 00:00:00
rhel-7-server-ansible-2.4-rpms | 2.3 kB 00:00:00
rhel-7-server-extras-rpms | 2.0 kB 00:00:00
rhel-7-server-ose-3.10-rpms | 2.3 kB 00:00:00
rhel-7-server-rpms | 2.0 kB 00:00:00
rhel-7-server-satellite-tools-6.3-rpms | 2.1 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package atomic-openshift-sdn-ovs.x86_64 0:3.10.72-1.git.0.3cb2fdc.el7 will be installed
--> Processing Dependency: atomic-openshift-node = 3.10.72-1.git.0.3cb2fdc.el7 for package: atomic-openshift-sdn-ovs-3.10.72-1.git.0.3cb2fdc.el7.x86_64
--> Processing Dependency: openvswitch >= 2.6.1 for package: atomic-openshift-sdn-ovs-3.10.72-1.git.0.3cb2fdc.el7.x86_64
--> Running transaction check
---> Package atomic-openshift-sdn-ovs.x86_64 0:3.10.72-1.git.0.3cb2fdc.el7 will be installed
--> Processing Dependency: atomic-openshift-node = 3.10.72-1.git.0.3cb2fdc.el7 for package: atomic-openshift-sdn-ovs-3.10.72-1.git.0.3cb2fdc.el7.x86_64
---> Package openvswitch.x86_64 0:2.9.0-70.el7fdp.1 will be installed
--> Processing Dependency: openvswitch-selinux-extra-policy for package: openvswitch-2.9.0-70.el7fdp.1.x86_64
--> Running transaction check
---> Package atomic-openshift-sdn-ovs.x86_64 0:3.10.72-1.git.0.3cb2fdc.el7 will be installed
--> Processing Dependency: atomic-openshift-node = 3.10.72-1.git.0.3cb2fdc.el7 for package: atomic-openshift-sdn-ovs-3.10.72-1.git.0.3cb2fdc.el7.x86_64
---> Package openvswitch-selinux-extra-policy.noarch 0:1.0-7.el7fdp will be installed
--> Finished Dependency Resolution
Error: Package: atomic-openshift-sdn-ovs-3.10.72-1.git.0.3cb2fdc.el7.x86_64 (rhel-7-server-ose-3.10-rpms)
Requires: atomic-openshift-node = 3.10.72-1.git.0.3cb2fdc.el7
Installed: atomic-openshift-node-3.10.14-1.git.0.ba8ae6d.el7.x86_64 (@rhel-7-server-ose-3.10-rpms)
atomic-openshift-node = 3.10.14-1.git.0.ba8ae6d.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Version:openshift-ansible-3.10.89-1.git.0.14ed1cb.el7.noarch.rpm Fresh install v3.10 ocp. # cat /etc/yum.conf |grep exclude exclude= atomic-openshift-tests atomic-openshift-hyperkube atomic-openshift-recycle atomic-openshift-pod atomic-openshift-node atomic-openshift-master atomic-openshift-clients-redistributable atomic-openshift-clients atomic-openshift docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* Version:openshift-ansible-3.10.90-1.git.0.5a504fb.el7.noarch.rpm # cat /etc/yum.conf|grep exclude exclude= atomic-openshift-tests atomic-openshift-hyperkube atomic-openshift-sdn-ovs atomic-openshift-recycle atomic-openshift-pod atomic-openshift-node atomic-openshift-master atomic-openshift-clients-redistributable atomic-openshift-clients atomic-openshift docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* So this bug fixed in v3.10.90+. Need drop from #38578(v3.10.89). Change status back to MODIFIED. Fix is in latest built packages. Checked that it had been fixed on openshift-ansible-3.10.109-1.git.0.3c11d4d.el7.noarch.rpm # cat /etc/yum.conf |grep exclude exclude= atomic-openshift-tests atomic-openshift-hyperkube atomic-openshift-sdn-ovs atomic-openshift-recycle atomic-openshift-pod atomic-openshift-node atomic-openshift-master atomic-openshift-clients-redistributable atomic-openshift-clients atomic-openshift docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* Change status to MODIFIED to wait for errata. Verified on openshift-ansible-3.10.111-1.git.0.84b2b69.el7.noarch.rpm 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-2019:0328 |