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.

Description of problem:
onboot SystemTap scripts does not work on RHEL8.
This used to work on RHEL7.

Version-Release number of selected component (if applicable):
systemtap-4.2-6.el8.x86_64
systemtap-devel-4.2-6.el8.x86_64
systemtap-client-4.2-6.el8.x86_64
systemtap-runtime-4.2-6.el8.x86_64
systemtap-initscript-4.2-6.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install SystemTap and systemtap-initscript
2. Try to enable a script on boot, for example:

# cp panic_at_bad_page.stp /etc/systemtap/script.d/

# systemtap-service onboot panic_at_bad_page
Could not find /sbin/new-kernel-pkg                        [FAILED]
This feature requires /sbin/new-kernel-pkg.
If it is located elsewhere, modify the $NEWKERNELPKG parameter

Actual results:
It fails due to missing /sbin/new-kernel-pkg on RHEL8.
I have not found any RPM that provides this file.

Yup, thanks, it was broken by rhel8 baseos changes in the boot ramdisk building system, plus the more thorough systemd/initscripts changes, and we haven't adapted systemtap to it all yet.

*** This bug has been marked as a duplicate of bug 1650594 ***