Bug 1825667

Summary: LIbvirt: OCP Bootstrap on s390x fails with etcd static pods dying with UNSUPPORTED_ARCH error
Product: OpenShift Container Platform Reporter: Prashanth Sundararaman <psundara>
Component: Etcd OperatorAssignee: Sam Batschelet <sbatsche>
Status: CLOSED ERRATA QA Contact: Prashanth Sundararaman <psundara>
Severity: medium Docs Contact:
Priority: high    
Version: 4.5CC: cbaus
Target Milestone: ---Keywords: Regression
Target Release: 4.5.0   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1831664 (view as bug list) Environment:
Last Closed: 2020-07-13 17:28:40 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:
Bug Depends On:    
Bug Blocks: 1831664    

Description Prashanth Sundararaman 2020-04-19 19:24:00 UTC 
Description of problem:
Tried a 4.4 libvirt install of OCP on an s390x system. Noticed that two new pods - etcd-metrics and etcd-member on the bootstrap node was dying with:

"etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=s390x set"

On talking to the etcd-team it looks like the Cluster-Etcd-Operator needs to add this environment variable when rendering the yaml for these pods.

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

How reproducible:
All the time

Steps to Reproduce:
OCP libvirt install on an s390x system. Do a "sudo crictl ps --all" on the
bootstrap node and "sudo crictl logs" on the etcd containers to notice the error.
Comment 4 ge liu 2020-05-08 03:35:30 UTC 
@Prashanth Sundararaman, could u help to tried it again? We have not env to cover ocp test on platform: s390s, thanks in advance!
Comment 5 errata-xmlrpc 2020-07-13 17:28:40 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