RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1269920 - kpatch-build missing
Summary: kpatch-build missing
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kpatch
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Josh Poimboeuf
QA Contact: Chunyu Hu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-08 13:37 UTC by Jeremy Harris
Modified: 2015-10-12 16:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-12 16:13:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jeremy Harris 2015-10-08 13:37:14 UTC
Description of problem:
  Neither the utility nor the manpage for kpatch-build can be found

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


How reproducible:
  100%


Steps to Reproduce:
1. (in a VM) RHEL7 install procedure per https://github.com/dynup/kpatch
2. sudo yum provides */*kpatch-build*
3.

Actual results:
  Loaded plugins: auto-update-debuginfo, langpacks, product-id, subscription-manager
  No matches found



Expected results:
  Usable kpatch installation

Additional info:

  kpatch itself is present, though I don't know if the above sequence installed
it or my original system installation:

  [jgh@rhel7 kpatch]$ which kpatch
  /usr/sbin/kpatch

Comment 2 Seth Jennings 2015-10-08 17:05:21 UTC
There is only a kpatch package for RHEL7, not a kpatch-build package.  There is currently no package in RHEL7 that includes the build-side utilities for kpatch.  The kpatch package only includes the apply-side utilities (i.e. the kpatch command).

In order to run kpatch-build:

1) Clone the github repo

git clone https://github.com/dynup/kpatch.git

2) Follow the README for "Install the dependencies for the "kpatch-build" command" in the RHEL7 section

https://github.com/dynup/kpatch#rhel-7

3) cd kpatch-build/ then invoke the kpatch-build script from there.

Comment 3 Jeremy Harris 2015-10-09 08:10:56 UTC
Those instructions do not appear to be sufficient:

 [jgh@rhel7 kpatch]$ kpatch-build ss.patch 
 ERROR: can't find supporting tools.

For added amusement, the manpage for kpatch references one for kpatch-build.

Comment 4 Josh Poimboeuf 2015-10-12 16:06:36 UTC
Jeremy,

Did you do "make" and "make install" first?

Comment 5 Josh Poimboeuf 2015-10-12 16:13:59 UTC
The missing kpatch-build RPM is by design.  kpatch-build is dangerous and should be used with care.  It isn't intended to be used by RHEL customers.  Any live patching done by customers should only be done with patch modules which have been built and signed internally at Red Hat.


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