Bug 984087

Summary: setcifsacl should still work when plugin can't be loaded
Product: [Fedora] Fedora Reporter: Jeff Layton <jlayton>
Component: cifs-utilsAssignee: Jeff Layton <jlayton>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: medium    
Version: rawhideCC: abokovoy, jhrozek, jlayton, ssorce, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cifs-utils-6.1-3.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 985067 (view as bug list) Environment:
Last Closed: 2013-07-25 00:51:01 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: 985067    

Description Jeff Layton 2013-07-12 17:50:25 UTC
Currently setcifsacl just returns an error if it can't load the plugin. It should instead allow a user to supply a "raw" SID string in that case. getcifsacl will already print them, so it's just a matter of accepting them in reverse.

Comment 1 Fedora Update System 2013-07-15 15:59:34 UTC
cifs-utils-6.1-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/cifs-utils-6.1-3.fc19

Comment 2 Fedora Update System 2013-07-17 03:05:57 UTC
Package cifs-utils-6.1-3.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cifs-utils-6.1-3.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-13079/cifs-utils-6.1-3.fc19
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2013-07-25 00:51:01 UTC
cifs-utils-6.1-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.