Bug 1795798

Summary:	Missing pcp-pmda-bpftrace and pcp-pmda-bcc packages for s390x and aarch64 architectures
Product:	Red Hat Enterprise Linux 8	Reporter:	Jan Kurik <jkurik>
Component:	pcp	Assignee:	Andreas Gerstmayr <agerstmayr>
Status:	CLOSED ERRATA	QA Contact:	Jan Kurik <jkurik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.2	CC:	agerstmayr, jkurik, mgoodwin, nathans, patrickm
Target Milestone:	rc	Keywords:	Bugfix, Triaged
Target Release:	8.2	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:40:28 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:

Description Jan Kurik 2020-01-28 21:52:23 UTC

Description of problem:
The latest, currently available PCP build 5.0.2-3.el8 is missing "pcp-pmda-bpftrace" package for s390x and aarch64 architectures.

Version-Release number of selected component (if applicable):
PCP build 5.0.2-3.el8

How reproducible:
Always

Steps to Reproduce:
1. Check the latest PCP build 5.0.2-3.el8

Actual results:
The pcp-pmda-bpftrace is built for x86_64 and ppc64le architectures only.

Expected results:
The pcp-pmda-bpftrace is built for all the supported architectures (x86_64, ppc64le, s390x, aarch64).

Comment 1 Nathan Scott 2020-01-28 22:52:47 UTC

Since this is a new sub-package in 8.2, and a simple fix, I propose we tackle it in this release rather than in 8.3.

Comment 2 Andreas Gerstmayr 2020-01-29 13:38:38 UTC

Fixed in upstream with:

commit bfc76ee9e23f370d3ea12323b5f1fa12d054300c
Author: Andreas Gerstmayr <agerstmayr>
Date:   Wed Jan 29 13:59:16 2020 +0100

    build: build pcp-pmda-bpftrace on all architectures supported by bpftrace


Waiting for #1795804 so we can publish one build with all related fixes.
Btw, I also synced the supported BCC architectures in upstream, should we create a separate BZ ticket for that?

commit d233dfdf1176a3715555a78c34f22bcb72436f14
Author: Andreas Gerstmayr <agerstmayr>
Date:   Wed Jan 29 14:04:57 2020 +0100

    build: build pcp-pmda-bcc on all architectures supported by bcc

Comment 3 Jan Kurik 2020-01-30 06:25:29 UTC

> Btw, I also synced the supported BCC architectures in
> upstream, should we create a separate BZ ticket for that?

I believe we can use this BZ to deliver both. I just modified the summary to reflect it.
Thanks Andreas.

Comment 4 Andreas Gerstmayr 2020-02-03 13:02:18 UTC

Resolved with latest build pcp-5.0.2-4.el8:

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=26174387
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=26174390

Comment 5 Nathan Scott 2020-02-03 22:45:14 UTC

This needs to be in MODIFIED for now, for addition to errata (later today).

Comment 7 Jan Kurik 2020-02-14 20:56:10 UTC

Fixed on PCP 5.0.2-4.el8 build.

Comment 9 errata-xmlrpc 2020-04-28 15:40:28 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/RHBA-2020:1628