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:

As per upstream, the current commit used on 1.0-rhel-8.0.0 branch d76078982e950bc962d5e4c1d64244309f61f908 introduces a regression. We should revert to the same commit as present on the rhel8-rhel-8.0.0 branch.

What is the effect of this regression? Do we need to backport this to the v1 stream in RHEL 8.X or is it not bad enough to prevent usage?

Hi Scott,

the plan is to revert to v0.3 to avoid this regression? Please confirm.

Thanks,
Jindrich

Check in upstream code:
commit d76078982e950bc962d5e4c1d64244309f61f908
Merge: 027f4e6 1533c9f
...

commit 1533c9f5962513f5ef90c28fddae6b01c5c3dbda

So the patch is 1533c9f is the patch we need to check and make sure is not included in the code. 

Check with the src package fuse-overlayfs-0.3-5.module+el8.1.0+3468+011f0ab0.src.rpm. The arg force_create for create_whiteout() from that patch is not included. So set this to verified.

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/RHSA-2019:3494