Bug 1610629

Summary: NetApp cDOT: Can't write into CIFS share
Product: Red Hat OpenStack Reporter: Goutham Pacha Ravi <gouthamr>
Component: openstack-manilaAssignee: Goutham Pacha Ravi <gouthamr>
Status: CLOSED ERRATA QA Contact: Dustin Schoenbrun <dschoenb>
Severity: low Docs Contact: mmurray
Priority: medium    
Version: 10.0 (Newton)CC: amcleod, gouthamr, knylande, sclewis, tbarron
Target Milestone: z9Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: openstack-manila-3.0.0-13.el7ost Doc Type: Bug Fix
Doc Text:
Previously, the security style of CIFS shares that were provisioned with the NetApp driver was incorrect. As a result of this, users were unable to write data to CIFS shares, even with explicit 'rw' access. With this update, the security style of the NetApp ONTAP driver is always 'ntfs' on CIFS shares, and users that request 'rw' access with Manila can write data to CIFS shares successfully.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-17 17:00:45 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:

Description Goutham Pacha Ravi 2018-08-01 05:13:13 UTC 
Description of problem:

Cannot write into CIFS share backed by NetApp 

Version-Release number of selected component (if applicable): Newton / OSP 10


How reproducible:


Steps to Reproduce:
1. Create a share network, assign a security service (Active Directory) to share network
2. Create a cifs share with share server management.
3. Add user level "rw" access and mount the share on the host
4. Mount the share and attempt to write into the share

Actual results:

You will notice that the share can be read from, however, can't be written into.


Expected results:
Share should be writable

Additional info:
Comment 11 errata-xmlrpc 2018-09-17 17:00:45 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-2018:2671