Bug 2006841

Summary:	rebase kpatch user utility code to v0.9.4
Product:	Red Hat Enterprise Linux 8	Reporter:	Joe Lawrence <joe.lawrence>
Component:	kpatch	Assignee:	Artem Savkov <asavkov>
kpatch sub component:	kpatch-utility	QA Contact:	zhijwang <zhijwang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	bhu, kpatch-maint, rhandlin, ykopkova
Version:	8.6	Keywords:	Rebase, Triaged
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kpatch-0.9.4-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2008776 (view as bug list)		Environment:
Last Closed:	2022-05-10 14:55:34 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:	2008776

Description Joe Lawrence 2021-09-22 14:04:55 UTC

rhel-8.5 shipped with kpatch utility v0.9.2, what has changed in the file since then:

$ git log v0.9.2~1..master --oneline --no-decorate --no-merges -- kpatch/ contrib/kpatch.spec
bff258754c9a Bump to v0.9.4
df1e98f2c74b kpatch: rmmod module of the same name before loading a module
39f695bbb29c kpatch: use /sys/kernel/kpatch/ to check whether core module is loaded
17539e71e7ac kpatch: Sync signal subcmd usage output with manpage
35b771712e69 Bump to v0.9.3
47c1bd435a49 kpatch: cleanup install directory
b470e5091d86 kpatch: Inform user when signal subcommand is unnecessary
cdee6bd650a3 kpatch: wait for module ref counts on unload
60523a99762e Bump to v0.9.2

These are all minor cleanups, but let's use the minor release as an opportunity to keep up and rebase to v0.9.4

Comment 1 Artem Savkov 2021-09-23 10:17:12 UTC

Since we don't have a separate component for kpatch-dnf I assume this should be also used to update that to v0.4?

Comment 2 Joe Lawrence 2021-09-23 12:59:08 UTC

(In reply to Artem Savkov from comment #1)
> Since we don't have a separate component for kpatch-dnf I assume this should
> be also used to update that to v0.4?

Ah good catch, I think it makes sense to do the update for kpatch-dnf here as well.

Since there is no PR for the tagging, I'll note here a small type: "kpath-dnf-v0.4".  GitHub has an "edit" feature if you want to try it.. I don't know if that will require any force pulls or what the impact will be.  Maybe "releases" are purely a server-side concept?

Comment 3 Artem Savkov 2021-09-23 13:20:48 UTC

> Since there is no PR for the tagging, I'll note here a small type: "kpath-dnf-v0.4".  GitHub has an "edit" feature if you want to try it.. I don't know if that will require any force pulls or what the impact will be.  Maybe "releases" are purely a server-side concept?

I think so, I edited it without any issues, the only thing we have in git is the tag, and it is different - v0.4 so we are fine.

Comment 13 errata-xmlrpc 2022-05-10 14:55:34 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 (kpatch 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:1987