Bug 2035899 - Operator-sdk run bundle doesn't support arm64 env
Summary: Operator-sdk run bundle doesn't support arm64 env
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Operator SDK
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Jesus M. Rodriguez
QA Contact: Fan Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-28 12:12 UTC by Fan Jia
Modified: 2022-08-10 10:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Allow building arm64 operators Reason: Support arm64 architecture Result: Operator-sdk now supports building operator images targeted at arm64.
Clone Of:
Environment:
Last Closed: 2022-08-10 10:41:05 UTC
Target Upstream Version:
Embargoed:
jesusr: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:41:27 UTC

Comment 1 Prashanth Sundararaman 2022-01-04 16:06:53 UTC 
quay.io/olmqe/blacklist-bundle:testarm64 seems to be an amd64 image, not arm64.
Comment 6 Jesus M. Rodriguez 2022-02-09 21:16:21 UTC 
I was right in comment #3, opm did not yet support arm64 until release 1.20. 

The scenario is that we try to download opm and there was no arm64 opm until release 1.20.
* see release 1.20 has arm64 binaries: https://github.com/operator-framework/operator-registry/releases/tag/v1.20.0
* see that prior to 1.20 there were no arm64 binaries: https://github.com/operator-framework/operator-registry/releases/tag/v1.19.5

moving this bug to 4.11 when we can better support arm64 .
Comment 7 Jesus M. Rodriguez 2022-04-07 04:00:06 UTC 
operator-sdk v1.19.0 upstream will have the newer opm, then we can revisit arm64 across the board.
Comment 8 Fan Jia 2022-04-28 06:37:49 UTC 
opm:latest support arm64 now. verified. run bundle success in arm cluster.
operator-sdk version: "v1.18.1-ocp", commit: "1d8c39dd75680daaf911c10582cf755c5f16da5b", kubernetes version: "v1.22", go version: "go1.17.4", GOOS: "linux", GOARCH: "amd64"
operator-sdk run bundle quay.io/olmqe/xxxxx-bundle:V4.10
INFO[0060] Successfully created registry pod: quay-io-olmqe-xxxxx-bundle-v4-10 
INFO[0061] Created CatalogSource: xxxxx-catalog     
INFO[0061] OperatorGroup "operator-sdk-og" created      
INFO[0062] Created Subscription: xxxxx-v0-0-1-sub   
INFO[0073] Approved InstallPlan install-4j2ch for the Subscription: xxxxx-v0-0-1-sub 
INFO[0073] Waiting for ClusterServiceVersion "default/xxxxx.v0.0.1" to reach 'Succeeded' phase 
INFO[0073]   Waiting for ClusterServiceVersion "default/xxxxx.v0.0.1" to appear 
INFO[0085]   Found ClusterServiceVersion "default/xxxxx.v0.0.1" phase: Pending 
INFO[0087]   Found ClusterServiceVersion "default/xxxxx.v0.0.1" phase: Installing 
INFO[0117]   Found ClusterServiceVersion "default/xxxxx.v0.0.1" phase: Succeeded 
INFO[0117] OLM has successfully installed "xxxxx.v0.0.1"
Comment 10 errata-xmlrpc 2022-08-10 10:41:05 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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.

https://access.redhat.com/errata/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.