Flight recorder service, trace-cmd.service, provides a feature to
automatically start trace-cmd command at every system start-up and to
automatically reload trace-cmd command at every kernel module loading
to enable tracepoints provided by kernel modules.
Thanks to this feature, once system panic occurs, users retrieve
ftrace ring buffer from crash dump that is created by some crash dump
mechanism such as kdump and virsh dump using crash trace command [1]
and can perform failure analysis based on ftrace event logs.
Historically, this feature has been provided only in the RHEL7 and
RHEL8 versions of trace-cmd packages so far. However, with the
introduction of CentOS Stream, RHEL's development process changed and
now CentOS Stream is an upstream of RHEL and Fedora Linux is the
upstream of CentOS Stream [2], due to which, Red Hat now follows
upstream-first policy strictly and requires this feature be provided
in its upstream.
[1] https://src.fedoraproject.org/rpms/crash-trace-command
[2] https://www.redhat.com/en/topics/linux/what-is-centos-stream
Resolves: rhbz#2070600
Signed-off-by: KUDOH Takashi <t-kudoh@fujitsu.com>
Signed-off-by: HATAYAMA Daisuke <d.hatayama@fujitsu.com>
Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
libtracecmd contains an empty DT_RPATH tag. It doesn't make the
runpath check fail, but annocheck complains about it. Remove that
rpath too.
Related: rhbz#1978504
Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
Two rpminspect gating test fails: runpath and annocheck. The first one
is fixed by running chrpath. The second by not ignoring LDFLAGS when
building the shared libs.
Related: rhbz#1978504
Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
