Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1834892

Summary:	Prometheus-operator ARCH is hardcoded to amd64
Product:	OpenShift Container Platform	Reporter:	Andy McCrae <amccrae>
Component:	Monitoring	Assignee:	Pawel Krupa <pkrupa>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.5.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:37:59 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 Andy McCrae 2020-05-12 15:29:42 UTC

Description of problem:
After 4.4 the ARCH and OS in the Makefile were defaulted to amd64/linux upstream - this means that any multi-arch builds are built amd64 and fail to run successfully on 4.5+

Version-Release number of selected component (if applicable):
4.5

How reproducible:
Consistently

Steps to Reproduce:
1. Build prometheus-operator or prometheus-config-reloader on non-x86_64 machine.
2. Attempt to run the image 

Actual results:

exec format error

Expected results:

The image runs successfully.

Additional info:

A fix is upstream in coreos/prometheus-operator: https://github.com/coreos/prometheus-operator/commit/fcdb5027b58d9dded99fb18bcd2c7b1032ff9e97 but this won't be included in 4.5, there is a PR up already to fix this downstream: https://github.com/openshift/prometheus-operator/pull/71/files

Comment 3 Junqi Zhao 2020-05-15 10:26:47 UTC

LGTM with 4.5.0-0.nightly-2020-05-14-190315

Comment 4 errata-xmlrpc 2020-07-13 17:37:59 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, 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:2409