Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2081325

Summary:	Add measurement and load location information to the run summary report
Product:	Red Hat Enterprise Linux 9	Reporter:	Clark Williams <williams>
Component:	rteval	Assignee:	Leah Leshchinsky <lleshchi>
Status:	CLOSED ERRATA	QA Contact:	Waylon Cude <wcude>
Severity:	medium	Docs Contact:	Sujata Kurup <skurup>
Priority:	unspecified
Version:	9.2	CC:	bhu, jkacur, mstowell, qzhao, rt-maint, skurup
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	rteval-3.4-4.el9	Doc Type:	Enhancement
Doc Text:	.The `rteval` command output now includes the program loads and measurement threads information The `rteval` command now displays a report summary with the number of program loads, measurement threads, and the corresponding CPU that ran these threads. This information helps to evaluate the performance of a real-time kernel under load on specific hardware platforms. The `rteval` report is written to an XML file along with the boot log for the system and saved to the `rteval-<date>-N-tar.bz2` compressed file. The `date` specifies the report generation date and `N` is the counter for the Nth run. To generate an `rteval` report, enter the following command: ---- # rteval --summarize rteval-<date>-N.tar.bz2 ----	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 07:18:14 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:
Bug Blocks:	2119171

Description Clark Williams 2022-05-03 13:01:26 UTC

Description of problem:

The run report produced a the end of the run does *not* contain information on where load and measurement threads were run. 


Version-Release number of selected component (if applicable):
# rpm -q rteval
rteval-3.3-3.el9.noarch

How reproducible:
always

Additional info:

We need to ensure that the two messages below from run startup make it into the summary report.

# rteval --duration=12h --loads-cpulist=0-5 --measurement-cpulist=6-11 
got system topology: 2 node system (6 cores per node)
rteval run on 5.18.0-0.rc5.40.test.eln118.x86_64+rt started at Tue May  3 08:50:32 2022
started 3 loads on cores 0-5  with 2 numa nodes
started measurement threads on cores 6-11
Run duration: 43200.0 seconds

Comment 10 errata-xmlrpc 2023-05-09 07:18:14 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 (rteval bug fix and enhancement update), 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-2023:2149