Bug 2076501

Summary:	delve fails with "Version of Delve is too old for this version of Go"
Product:	Red Hat Enterprise Linux 8	Reporter:	Edjunior Barbosa Machado <emachado>
Component:	delve	Assignee:	Alejandro Sáez Morollón <asm>
Status:	CLOSED ERRATA	QA Contact:	Edjunior Barbosa Machado <emachado>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.7	CC:	asm, sipoyare
Target Milestone:	rc	Keywords:	Bugfix, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	go-toolset:rhel8:8070020220503122809:347cc21f	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	2098063 (view as bug list)		Environment:
Last Closed:	2022-11-08 09:30:17 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:	2098063

Description Edjunior Barbosa Machado 2022-04-19 08:22:34 UTC

Description of problem:
delve initialization on rhel-8.7 fails with the following message:

[root@sheep-1 delve]# dlv debug 
Version of Delve is too old for this version of Go (maximum supported version 1.17, suppress this error with --check-go-version=false)

It works as expected if the suggested workaround is used (--check-go-version=false).

Version-Release number of selected component (if applicable):
go-toolset:rhel8:8070020220414195051:347cc21f
golang-1.18.0-1.module+el8.7.0+14844+3c99e33e
delve-1.7.2-1.module+el8.6.0+12972+ebab5911
RHEL-8.7.0-20220418.0

Steps to Reproduce:
1. dlv debug

Comment 1 Edjunior Barbosa Machado 2022-04-22 08:44:23 UTC

Also reproducible with latest go-toolset:rhel8:8070020220419133936:347cc21f.

Comment 8 errata-xmlrpc 2022-11-08 09:30:17 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 (go-toolset:rhel8 bug fix and enhancement 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/RHBA-2022:7522