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 1378469 - Don't expect kernel's version '2.6.*' or '3.*.*'
Summary: Don't expect kernel's version '2.6.*' or '3.*.*'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: abrt
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: abrt
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks: 1381083
TreeView+ depends on / blocked
 
Reported: 2016-09-22 13:25 UTC by Matej Habrnal
Modified: 2017-08-01 18:15 UTC (History)
4 users (show)

Fixed In Version: abrt-2.1.11-46.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 18:15:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch 1/2: lib: don't expect kernel's version '2.6.*' or '3.*.*' (2.85 KB, patch)
2017-02-14 12:13 UTC, Matej Habrnal
no flags Details | Diff
Patch 2/2: koops: do not assume version has 3 levels (2.48 KB, patch)
2017-02-14 12:13 UTC, Matej Habrnal
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1927 0 normal SHIPPED_LIVE abrt, abrt-java-connector, libreport bug fix update 2017-08-01 18:07:39 UTC

Description Matej Habrnal 2016-09-22 13:25:10 UTC
Description of problem:
The function parsing kernel's version was expecting one of the strings
mentioned in Summary. Unfortunately, none of them appears in oopses for
kernel-4.*.*

For instance, if the kernel is in version 4.5.0-3.el7.aarch64, koops_extract_version() matches the kernel version as 3.el7.aarch64 (expects the version starts with 3.*.) This causes abrt remove oops dump directory because a tool abrt-action-save-package-data can't find information about package kernel-3.el7.aarch64.

In case the kernel is in version 4.5.0-2.el7.aarch64, koops_extract_version() don't match the version as valid and uname -r version is used instead.


Additional info:
Upstream patches:
https://github.com/abrt/abrt/commit/9023d77ad5539433146b59e5ac80e3cefcb20cf7
https://github.com/abrt/abrt/commit/197a39938e57b2a3e8487613d62e0edf39d4d29c

Comment 2 Matej Habrnal 2017-01-26 12:58:16 UTC
Opened upstream pull request https://github.com/abrt/abrt/pull/1223

Comment 4 Matej Habrnal 2017-02-14 12:13:25 UTC
Created attachment 1250198 [details]
Patch 1/2: lib: don't expect kernel's version '2.6.*' or '3.*.*'

Comment 5 Matej Habrnal 2017-02-14 12:13:29 UTC
Created attachment 1250199 [details]
Patch 2/2: koops: do not assume version has 3 levels

Comment 7 errata-xmlrpc 2017-08-01 18:15:18 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-2017:1927


Note You need to log in before you can comment on or make changes to this bug.