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 1824324 - initscripts: incompatibility with grep 3.2+
Summary: initscripts: incompatibility with grep 3.2+
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: initscripts
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Jan Macku
QA Contact: Daniel Rusek
Depends On:
TreeView+ depends on / blocked
Reported: 2020-04-15 20:40 UTC by Carl George 🤠
Modified: 2020-11-04 01:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-04 01:41:25 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4463 0 None None None 2020-11-04 01:41:39 UTC

Description Carl George 🤠 2020-04-15 20:40:01 UTC
Description of problem:
Initscripts prior to 10.03 has a bug when used with grep 3.2 or newer.


CentOS 8 and RHEL 8 are using initscripts 10.00.6 and grep 3.1, but some users choose to upgrade to a newer version of grep on their own and hit this bug.  This will also be a problem if RHEL chooses to rebase grep or backport that behavior in the future.

Version-Release number of selected component (if applicable):

Additional info:
The community has offered a backport already.


Comment 1 Carl George 🤠 2020-04-15 20:46:26 UTC
Please disregard that last link in the additional info.  That's a patch that would apply to the CentOS initscripts package source, not to the initscripts source itself.  The appropriate patch to apply in the RHEL spec file would be the upstream one.


Comment 2 Jan Macku 2020-04-16 06:32:18 UTC
Hi Carl,
thank you, I completely forgot about this issue. I'll backport it from upstream. I should make it into RHEL 8.3.0.


Comment 3 Jan Macku 2020-04-16 08:03:47 UTC
Upstream PR: https://github.com/fedora-sysv/initscripts/pull/317

Comment 5 Davide Cavalca 2020-05-20 15:34:53 UTC
Any update on this? fwiw I had a chat with grep upstream and they've confirmed the PR will properly mitigate this issue.

Comment 6 Lukáš Nykrýn 2020-05-20 15:45:29 UTC
(In reply to Davide Cavalca from comment #5)
> Any update on this? fwiw I had a chat with grep upstream and they've
> confirmed the PR will properly mitigate this issue.

The fix is planned for 8.3.

Comment 12 errata-xmlrpc 2020-11-04 01:41:25 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 (initscripts 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.


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