Bug 1341786

Summary: tar silently ignores --xattrs-exclude during archive creation
Product: Red Hat Enterprise Linux 7 Reporter: Ian McLeod <imcleod>
Component: tarAssignee: Tomas Repik <trepik>
Status: CLOSED ERRATA QA Contact: Robin Hack <rhack>
Severity: unspecified Docs Contact: Lenka Kimlickova <lkimlick>
Priority: unspecified    
Version: 7.2CC: kvolny, praiskup, rhack, trepik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
"tar" options "--xattrs-exclude" and "--xattrs-include" no longer ignored Previously, the "tar" command ignored the "--xattrs-exclude" and "--xattrs-include" options. To fix this bug, "tar" has been modified to apply include and exclude masks when fetching extended attributes. As a result, the "--xattrs-exclude" and "--xattrs-include" options are no longer ignored.
Story Points: ---
Clone Of:
: 1341787 (view as bug list) Environment:
Last Closed: 2017-08-01 17:01:03 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: 1341787, 1393868, 1400961    

Description Ian McLeod 2016-06-01 18:44:01 UTC
Description of problem:

When creating archives tar silently ignores --xattrs-exclude options.  More details, and a proposed patch can be found on the upstream mailing list here:

http://lists.gnu.org/archive/html/bug-tar/2016-05/msg00032.html


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

All 1.28 versions and, it seems, all versions since this CLI option was added.

How reproducible:

Always.

Comment 2 Pavel Raiskup 2016-06-02 06:50:16 UTC
It would be nice to have it upstream first, though it is simple enough
and straight-forward patch (likely will be applied unchanged sooner or later)
so I believe we could go downstream first in this case.

Comment 12 errata-xmlrpc 2017-08-01 17:01:03 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, 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-2017:2012