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.

This is related to the cancel_func changes, and the fix is already upstream in these commits:

9041174142e138aff13dcc23b46e4c53e1c410dd
1c731b561887a1f62697495ecb70942d335828fd

This will prevent livemedia-creator from being used with a boot.iso, only --no-virt mode will work.

This bug has been copied as 8.0.0 z-stream (EUS) bug # 1690507 zstream and now must be
resolved in the current update release, set blocker flag.

--------------------------------------------------------------------------------

                    This bug is a 0day bug. A fix for this bug must be committed to ystream before
                    the fix is delivered via zstream.
                    
                    It is probable there is no git branch on ystream yet. If this is the case,
                    please contact RCM team using Request Tracker tool
                    https://engineering.redhat.com/rt/Ticket/Create.html?Queue=7 and provide them
                    with the following information:
                    * Name of the git repository on Dist-Git
                    * Component
                    * Requested ystream branch
                    * ID of this bug (BZ Y stream )

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-2019:3328