Bug 1700877
Summary: | [stream 1.0] need to revert fuse-overlayfs commit to sync with rhel8 stream | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Lokesh Mandvekar <lsm5> | |
Component: | fuse-overlayfs | Assignee: | Giuseppe Scrivano <gscrivan> | |
Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 8.0 | CC: | ddarrah, dornelas, jnovy, jwboyer, lsm5, smccarty, toneata, ypu | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | 8.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1720707 (view as bug list) | Environment: | ||
Last Closed: | 2019-11-05 21:25:46 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1720707, 1734574 |
Description
Lokesh Mandvekar
2019-04-17 14:22:13 UTC
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 |