Bug 1915068 - Build operator-registry with golang-1.15
Summary: Build operator-registry with golang-1.15
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Evan Cordell
QA Contact: Jian Zhang
Depends On: 1909464
TreeView+ depends on / blocked
Reported: 2021-01-11 20:57 UTC by Yaakov Selkowitz
Modified: 2021-03-02 04:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1909464
Last Closed: 2021-03-02 04:48:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ocp-build-data pull 833 0 None open [openshift-4.6] Build operator-registry with golang-1.15 2021-02-17 22:36:52 UTC
Github operator-framework operator-registry pull 547 0 None closed [release-4.6] Bug 1915068: Fix windows build with golang 1.15 2021-02-20 01:26:00 UTC
Red Hat Product Errata RHBA-2021:0634 0 None None None 2021-03-02 04:48:28 UTC

Description Yaakov Selkowitz 2021-01-11 20:57:41 UTC
+++ This bug was initially created as a clone of Bug #1909464 +++

operator-registry is the only OpenShift container currently building with golang 1.14 due to cross-compilation issues with 1.15.  Now that golang-builder has been updated to 1.15.5, which fixes the darwin cross-compile issue, adding a workaround for https://github.com/golang/go/issues/40795 to the windows build will allow switching to 1.15.

Comment 3 Jian Zhang 2021-02-20 02:21:31 UTC
1, This base image contains the fixed PR:
[root@preserve-olm-env data]# docker inspect registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry:v4.6|grep "io.openshift.build"
                "io.openshift.build.commit.id": "56a73fe509cde3eb89c3d73e6e243cb66403c93f",
                "io.openshift.build.commit.url": "https://github.com/openshift/images/commit/56a73fe509cde3eb89c3d73e6e243cb66403c93f",
                "io.openshift.build.source-location": "https://github.com/openshift/images",
                "io.openshift.build.commit.id": "4c884cc4e9321a66144f02f81a967dd2706828f2",
                "io.openshift.build.commit.url": "https://github.com/operator-framework/operator-registry/commit/4c884cc4e9321a66144f02f81a967dd2706828f2",
                "io.openshift.build.source-location": "https://github.com/operator-framework/operator-registry",

2, Create a CatalogSource image by using above base image.
[root@preserve-olm-env data]# oc adm catalog build --appregistry-org="olmqe" --auth-token="basic xxx" --from="registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry:v4.6" --to=quay.io/olmqe/art:4.6
using registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry:v4.6 as a base image for buildingINFO[0003] loading Bundles                               dir=/tmp/cache-386259139/manifests-403778152
Uploading 144.4MB ...
Pushed sha256:a0f8c56861a59a4adf72cf8d0f50f9b83b30d6f01f452bdd00721811f7216987 to quay.io/olmqe/art:4.6

3, Create a CatalogSoruce CR to consume this image.
[root@preserve-olm-env data]# cat cs.yaml 
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
  name: olm
  namespace: openshift-marketplace
  displayName: OLM Operators
  image: quay.io/olmqe/art:4.6
  publisher: OLM QE
  sourceType: grpc
[root@preserve-olm-env data]# oc create -f cs.yaml 
catalogsource.operators.coreos.com/olm created

4, Check the packagemanifest
[root@preserve-olm-env data]# oc get packagemanifest|grep OLM
couchbase-enterprise-test                            OLM Operators          48s
descheduler-test                                     OLM Operators          48s

LGTM, verify it.

Comment 6 errata-xmlrpc 2021-03-02 04:48:10 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 (OpenShift Container Platform 4.6.19 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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