Bug 1909464 - 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.7.0
Assignee: Evan Cordell
QA Contact: Jian Zhang
Depends On:
Blocks: 1915068
TreeView+ depends on / blocked
Reported: 2020-12-20 07:24 UTC by Yaakov Selkowitz
Modified: 2021-02-24 15:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1915068 (view as bug list)
Last Closed: 2021-02-24 15:47:16 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ocp-build-data pull 804 0 None closed Build operator-registry with golang-1.15 2021-02-20 01:26:34 UTC
Github operator-framework operator-registry pull 541 0 None closed Bug 1909464: Fix windows build with golang 1.15 2021-02-20 01:26:35 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:47:59 UTC

Description Yaakov Selkowitz 2020-12-20 07:24:57 UTC
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 4 Jian Zhang 2021-01-15 10:18:47 UTC
1, This base image contains the fixed PR:
[root@preserve-olm-env operator-registry]# docker inspect registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry:v4.7
                "io.openshift.build.commit.id": "8e6c13fab15be609acdace4e981826091e7effd1",
                "io.openshift.build.commit.url": "https://github.com/operator-framework/operator-registry/commit/8e6c13fab15be609acdace4e981826091e7effd1",
                "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.7" --to=quay.io/olmqe/art:4.7
using registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry:v4.7 as a base image for buildingINFO[0002] loading Bundles                               dir=/tmp/cache-643585830/manifests-119899655
Uploading 146.7MB ...
Pushed sha256:642f1f184a56c7eb718d463d76f72181dbd3b908f9bead55a02bab94bdb058fb to quay.io/olmqe/art:4.7

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.7
  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
descheduler-test                                     OLM Operators                   5m17s
couchbase-enterprise-test                            OLM Operators                   5m17s

Looks good, verify it.
[root@preserve-olm-env data]# oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-01-14-211319   True        False         4h14m   Cluster version is 4.7.0-0.nightly-2021-01-14-211319

Comment 7 errata-xmlrpc 2021-02-24 15:47:16 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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.