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.

Description of problem:

dracut-049-209.git20220815.el8

80lvmthinpool-monitor module is backported from upstream, for module-setup.sh, it uses $SYSTEMCTL -q --root "$initdir" add-wants initrd.target start-thinpool-monitor.service. However $SYSTEMCTL is not suitable for rhel8, it should use systemctl instead. 

Because patch 18d36fabf5ab20404 ("feat(dracut.sh): allow overriding the systemctl command for sysroot") didn't backported to rhel8 dracut, so $SYSTEMCTL is unavailable.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Hi David,

Can this bz be fixed in rhel8.8? Since bz2034457 depends on this one, if the bug is planed to fixed in next release, then we will plan to defer bz2034457 to rhel8.9 as well.

Thanks,
Tao Liu

(In reply to ltao from comment #1)
> Can this bz be fixed in rhel8.8?

I'm pretty sure it can.

(In reply to David Tardon from comment #2)
> (In reply to ltao from comment #1)
> > Can this bz be fixed in rhel8.8?
> 
> I'm pretty sure it can.

OK, Thanks!

Hi Pavel,

Sorry to interrupt, since bz2034457 depends on this one, and bz2034457 is a feature bug. QE wants the feature bug to be fixed as early for testing, could you please get this bz fixed before ITM14? Thanks a lot!

Thanks,
Tao Liu

I've prepared a PR: https://github.com/redhat-plumbers/dracut-rhel8/pull/21

https://github.com/redhat-plumbers/dracut-rhel8/pull/23

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 (dracut 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:2994