Bug 1544689

Summary: Installed (but unpackaged) bpf related file(s) found
Product: Red Hat Enterprise Linux 7 Reporter: Martin Cermak <mcermak>
Component: systemtapAssignee: Frank Ch. Eigler <fche>
Status: CLOSED ERRATA QA Contact: Martin Cermak <mcermak>
Severity: low Docs Contact: Vladimír Slávik <vslavik>
Priority: low    
Version: 7.5-AltCC: bgollahe, dsmith, fche, jistone, jolsa, lberk, mcermak, mjw, vslavik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: systemtap-3.3-2.el7 Doc Type: Release Note
Doc Text:
This version of systemtap introduces limited support for eBPF tracing on x86-64. Use "stap --runtime=bpf FOO.stp" to test simple systemtap scripts, to run them as eBPF bytecodes instead of kernel modules. Many limitations of the kernel eBPF system and of its systemtap interface make only simple scripts work at this time. See the [man stapbpf] man page for more information.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:46:00 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: 1311586    
Bug Blocks: 1505884    

Description Martin Cermak 2018-02-13 10:03:21 UTC
There is a little packaging problem causing systemtap-3.2-4.el7.src.rpm to FTBFS on rhel-alt-7.5:

=======
    Installed (but unpackaged) file(s) found:
   /usr/bin/stapbpf
   /usr/share/man/man8/stapbpf.8.gz
=======

Comment 4 David Smith 2018-06-14 14:20:01 UTC
This bug is waiting on the kernel team to get the kernel-headers rpm with eBPF support in the rhel7.6 buildroots.

Comment 11 errata-xmlrpc 2018-10-30 10:46:00 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, 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/RHEA-2018:3168