Bug 1929359

Summary: etcd-quorum-guard uses origin-cli [4.8]
Product: OpenShift Container Platform Reporter: Yaakov Selkowitz <yselkowi>
Component: EtcdAssignee: Sam Batschelet <sbatsche>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: high Docs Contact:
Priority: high    
Version: 4.8CC: itsoiref, psundara, sbatsche
Target Milestone: ---Keywords: Regression
Target Release: 4.8.0   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 22:44:46 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 Yaakov Selkowitz 2021-02-16 17:55:51 UTC
The recent addition in 4.8 of single-node cluster support via https://github.com/openshift/cluster-etcd-operator/pull/527 contains an absolute image reference to the upstream origin-cli image.  Not only will this end up pulling an upstream image even in a downstream OCP build, it causes etcd-quorum-guard to crash on IBM P&Z architectures because upstream is amd64-only.

This needs to be fixed to respect the substitution of 'cli' from the payload.

Comment 2 Sam Batschelet 2021-02-16 18:37:51 UTC
nice catch yes when we moved the spec out of CVO control we did not remember to populate the image pull-spec from the release payload.

Comment 4 Prashanth Sundararaman 2021-02-17 14:38:58 UTC
verified w.r.t multi-arch on s390x with https://mirror.openshift.com/pub/openshift-v4/s390x/clients/ocp-dev-preview/4.8.0-0.nightly-s390x-2021-02-17-131252/ and the cli image used is the downstream image for OCP.

Comment 7 errata-xmlrpc 2021-07-27 22:44:46 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.8.2 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-2021:2438