+++ This bug was initially created as a clone of Bug #1782163 +++ Description of problem: Kuryr-Kubernetes uses OSP16 repositories to install its dependencies (mostly Python RPM's). As Kuryr is not part of OSP anymore, some of it dependencies (those not required by any other project) got removed from OSP16 and this causes Kuryr builds in OCP to fail. The correct approach here is to cross-tag those packages into OCP, because that solves some more issues: * OKD builds cannot have OSP16 packages. * OSP16 is not released before 4.3. That work is handled in Shared Content Request [1] and RCM ticket [2]. [1] https://mojo.redhat.com/docs/DOC-1212437 [2] https://projects.engineering.redhat.com/browse/RCM-72513 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Just check build results (upstream or downstream) 2. 3. Actual results: Builds fail with: - nothing provides python3-grpcio >= 1.12.0 needed by python3-kuryr-kubernetes-4.4.1-1.el7.noarch - nothing provides python3-kuryr-lib >= 0.5.0 needed by python3-kuryr-kubernetes-4.4.1-1.el7.noarch - nothing provides python3-protobuf >= 3.6.0 needed by python3-kuryr-kubernetes-4.4.1-1.el7.noarch Expected results: Builds complete normally. Additional info:
https://github.com/openshift/ocp-build-data/pull/253 is merged now and all the cross-tagging happened. This will get verified on the next build.
Verified in 4.3.0-0.nightly-2019-12-23-120031 on 2019-12-06.2 OSP 13 puddle. The OCP installer finishes successfully: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2019-12-23-120031 True False 13h Cluster version is 4.3.0-0.nightly-2019-12-23-120031 Kuryr cni and controller version: · kuryr-cni image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f863aecbc8cd8ea705e85edb3c35d8e2203061e5a34809039af7b55a42ccbab2 · kuryr-controller image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:6e1eaae900d00131a2a326971101039355ebd6eaa3027432746d50b8f47c8ba5
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-2020:0062