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.
DescriptionJuan Sebastian Castro
2022-07-15 15:31:37 UTC
Description of problem:
After migrating a RHEL 7 system sar data files (historic data) are not longer read by new sysstat version in RHEL 8.
"Current sysstat version cannot read the format of this file" (please see attached screenshot).
It'd be ideal to add a low rating warning message in leapp-report.txt file stating a conversion of all sa/sar files must be peformed after the migration because sysstat on RHEL 8 won't be able to read historic data.
Possible hint could be pointing to KCS https://access.redhat.com/solutions/5240511.
Version-Release number of selected component (if applicable):
leapp-repository-0.14.0-4.el7_9.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install sysstat on RHEL 7
yum install -y sysstat
2. Run sa1 command to collect and store binary data of system's activity.
/usr/lib64/sa/sa1 1 1
3. Read the sa## file generated
sar -f sa15
Linux 3.10.0-1160.el7.x86_64 (rhel79.domain.net) 07/15/2022 _x86_64_ (1 CPU)
03:13:18 PM CPU %user %nice %system %iowait %steal %idle
03:13:19 PM all 1.20 0.00 1.20 0.00 0.00 97.60
03:13:20 PM all 1.25 0.00 1.25 0.00 0.00 97.50
Average: all 1.21 0.00 1.21 0.00 0.00 97.57
4. Perform a migration RHEL 7 -> RHEL 8
5. Once in RHEL 8 try to read sa15 using sar command.
[root@rhel86 vagrant]# sar -f sa15
Invalid system activity file: sa15
File created by sar/sadc from sysstat version 10.1.5
Current sysstat version cannot read the format of this file (0x2171)
Actual results:
There isn't any low rate message warning about this.
Expected results:
A low risk warning message with a hint steps about how to convert the sa files.
Additional info:
Maybe including kcs https://access.redhat.com/solutions/5240511 in hints for further information.
Hi, thank you for the report and the link to the KCB. We have already opened a related BZ if I remember well and originally it was counted with the removal os sar files. However regarding the KCB it seems it could be resolved nowadays in better way. The solutio coule either of these two:
* report the required post-upgrade step (as in this ticket)
* or do the conversion automatically during the upgrade process so nothing has to be done by user
Comment 4RHEL Program Management
2023-09-12 12:23:55 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-12 13:21:15 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.