Description of problem: etcd does not support building unsupported upstream arch such as s390x. This is required for IBM Z. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Sam, do you have any advice for verify this bug, thanks.
Ge, This is what I did. First I grabbed an s390,s390x machine on beaker. Then as root export the following GOROOT=/usr/local/go GOPATH=/go PATH=${GOPATH}/bin:${GOROOT}/bin:${PATH} GO_DOWNLOAD_URL=https://storage.googleapis.com/golang GO_VERSION=1.11.12 This one-liner should get you a recent goloang 1.11.x $ rm -rf ${GOROOT} && curl -s ${GO_DOWNLOAD_URL}/go${GO_VERSION}.linux-s390x.tar.gz | tar -v -C /usr/local/ -xz && mkdir -p ${GOPATH}/src ${GOPATH}/bin && go version # install deps $ yum install -y make git ## test runtime ENV population $ mkdir -P $GOPATH/src/testing $ cd $GOPATH/src/testing $ curl -s https://gist.githubusercontent.com/hexfusion/fd098323a32dfa18e8ca02ff61f51743/raw/bf237b40b31c5d79f3acae6a226755ffe4bf305b/gistfile1.txt -o main.go go run main.go cat ENV ``` export ETCD_UNSUPPORTED_ARCH=s390x ``` ## test multiarch build $ git clone https://github.com/openshift/etcd.git $ cd etcd $ git checkout openshift-4.2 # build failure case $ make build [...] ./bin/etcd --version 2019-08-30 07:57:32.266697 E | etcdmain: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=s390x set. # valid build $ ./build # start failure case $ bin/etcd 2019-08-30 08:05:47.417816 E | etcdmain: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=s390x set. # valid start $ . ENV; bin/etcd bin/etcd 2019-08-30 08:05:18.089929 W | etcdmain: running etcd on unsupported architecture "s390x" since ETCD_UNSUPPORTED_ARCH is set 2019-08-30 08:05:18.090128 I | etcdmain: etcd Version: 3.3.10 2019-08-30 08:05:18.090134 I | etcdmain: Git SHA: 3ebe3d9 2019-08-30 08:05:18.090140 I | etcdmain: Go Version: go1.11.12 2019-08-30 08:05:18.090145 I | etcdmain: Go OS/Arch: linux/s390x [..]
sam, thanks, LGTM
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-2019:2922
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days