-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.10.0
-
None
-
None
-
Proposed
-
False
-
Description of problem:
Building the installer image started to fail on ppc64le
Version-Release number of selected component (if applicable):
4.10.0
How reproducible:
Always on the brew builders
Steps to Reproduce:
1. 2. 3.
Actual results:
2022-11-14 11:55:00,819 - atomic_reactor.tasks.binary_container_build - INFO - + go build -mod=vendor -ldflags ' -X github.com/openshift/installer/pkg/version.Raw=v4.10.0 -X github.com/openshift/installer/pkg/version.Commit=4e8922c14379dce4845f362ac3a83ff80f1dc655 -X github.com/openshift/installer/pkg/version.defaultArch=ppc64le -s -w' -tags ' release' -o bin/openshift-install ./cmd/openshift-install 2022-11-14 11:58:01,556 - atomic_reactor.tasks.binary_container_build - INFO - # github.com/openshift/installer/cmd/openshift-install 2022-11-14 11:58:01,556 - atomic_reactor.tasks.binary_container_build - INFO - github.com/aliyun/alibaba-cloud-sdk-go/services/cms.(*Client).DescribeMonitoringAgentHostsWithChan.func1: direct call too far: runtime.duffzero+1f0-tramp0 -20000e8
Expected results:
Successful build
Additional info:
This could potentially be a golang issue. After some preliminary investigation, we tried setting `-linkmode=external` in the ldflags which seems to allow the build to finish. So while we investigate the real cause of the issue, changing the link mode will serve as a workaround to unblock the build pipeline.