Bug 2105937 - telemeter golangci-lint outdated blocking ART PRs that update to Go1.18
Summary: telemeter golangci-lint outdated blocking ART PRs that update to Go1.18
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Joao Marcal
QA Contact: Junqi Zhao
Depends On: 2104549
TreeView+ depends on / blocked
Reported: 2022-07-11 09:12 UTC by Joao Marcal
Modified: 2022-08-10 11:21 UTC (History)
3 users (show)

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

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift telemeter pull 414 0 None open Bug 2105937:[release-4.11] Updates version of golangci-lint to support GO1.18 2022-07-11 09:20:39 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:21:09 UTC

Description Joao Marcal 2022-07-11 09:12:44 UTC
+++ This bug was initially created as a clone of Bug #2104549 +++

Description of problem:
telemeter project uses golangci-lint to lint golang files, however, we are currently running a version which is not supported in golang 1.18. This blocked an automatic PR from the ART team to update the golang version telemeter was using to 1.18.

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

How reproducible: always

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 3 Junqi Zhao 2022-07-13 03:34:05 UTC
tested with 4.11.0-0.nightly-2022-07-12-130219, fix is in the build and no regression issue

Comment 5 errata-xmlrpc 2022-08-10 11:20:54 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.


Note You need to log in before you can comment on or make changes to this bug.