Bug 2085187 - installer-artifacts fails to build with go 1.18
Summary: installer-artifacts fails to build with go 1.18
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.11
Hardware: All
OS: Mac OS
high
high
Target Milestone: ---
: 4.11.0
Assignee: Nobody
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-12 20:39 UTC by Yaakov Selkowitz
Modified: 2022-08-10 11:11 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:11:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5896 0 None open Bug 2085187: terraform: revendor golang.org/x/sys 2022-05-12 20:39:25 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:11:48 UTC

Description Yaakov Selkowitz 2022-05-12 20:39:03 UTC 
installer-artifacts fails to build with go 1.18, specifically during the Mac OS cross-builds, due to outdated golang.org/x/sys modules in terraform-provider-random and terraform-provider-ignition.  (Note that the native Linux installer build succeeds with 1.18.)  Updates to each are needed to fully migrate 4.11 to go 1.18.
Comment 3 Gaoyun Pei 2022-06-04 08:20:11 UTC 
Tested with openshift-install-mac-4.11.0-0.nightly-2022-06-03-121459 on macOS 12.3.1
Cluster creation and destroy both work well, no regression issue found.
Comment 6 errata-xmlrpc 2022-08-10 11:11:36 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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069
Note You need to log in before you can comment on or make changes to this bug.