Bug 1446325
| Summary: | [RHEL6 CIFS] After upgrading to latest samba 3.3.0 re-bease packages cifs mount is failing | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vivek Das <vdas> |
| Component: | doc-Administration_Guide | Assignee: | Laura Bailey <lbailey> |
| doc-Administration_Guide sub component: | 3.2 Release | QA Contact: | Vivek Das <vdas> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | amukherj, anoopcs, asriram, asrivast, madam, pgurusid, rhinduja, rhs-bugs, rhs-smb, rtalur, sanandpa, sprabhu, storage-doc, vdas |
| Version: | rhgs-3.3 | Keywords: | Regression |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-21 04:28: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: | 1417157 | ||
|
Description
Vivek Das
2017-04-27 16:24:17 UTC
(In reply to Vivek Das from comment #0) > mount: block device \\10.70.42.187\gluster-saturday-saturday is > write-protected, mounting read-only > mount: cannot mount block device \\10.70.42.187\gluster-saturday-saturday > read-only I somehow could not relate this error with cifs and samba. Can you please make sure that cifs-utils is installed on the system? (In reply to Anoop C S from comment #5) > (In reply to Vivek Das from comment #0) > > mount: block device \\10.70.42.187\gluster-saturday-saturday is > > write-protected, mounting read-only > > mount: cannot mount block device \\10.70.42.187\gluster-saturday-saturday > > read-only > > I somehow could not relate this error with cifs and samba. Can you please > make sure that cifs-utils is installed on the system? One can do a cifs mount even without installing cifs-utils by using -o username,password options. But still i am unable to do a cifs mount even after installing cifs-utils. Hi Rahul, We need to put this in release notes as well. So do i have to create a new bugzilla for the same? As per https://bugzilla.redhat.com/show_bug.cgi?id=1445633#c15 here is the summary cifs mount on a RHEL 6 machine will fail if the Samba server version is >= 4.6.3-2. Changing the default settings in smb.conf is a bad practice. We won't change it. We have to notify clients that if they want to mount shares on RHEL 6 machines using cifs then they must use "sec=ntlmssp" option. Note: it is ntlmssp and not just ntlm. Agree on Comment 25. As tried and tested with "sec=ntlm" on cifs mount command the mount fails whereas with "sec=ntlmssp" on cifs mount command the mount succeeds. All this over RHEL6 I would say it needs to go in both the places. 1. It should go in Release notes because it is a change of behavior; command which used to work up till now, would start failing once samba is updated. 2. Yes, admin guide has to be updated. Specifically, it is command under a. step 2 of "Mounting a Volume Manually using SMB on Red Hat Enterprise Linux" in section 6.3.3.1. MANUALLY MOUNTING VOLUMES USING SMB ON RED HAT ENTERPRISE LINUX AND WINDOWS b. step 2 of "Mounting a Volume Automatically using SMB on Red Hat Enterprise Linux " in section 6.3.3.2. AUTOMATICALLY MOUNTING VOLUMES USING SMB ON RED HAT ENTERPRISE LINUX AND WINDOWS While more secure defaults are a good thing, it sounds as though the move to this new samba version introduces what amounts to a 'breaking change' between RHEL6 releases, so we're seeing an error with RHGS similar to if the customer had moved from RHEL6-based gluster to RHEL7-based gluster. IMO this should be reverted in RHEL6 so that the 'breaking change' is not introduced. If we can't revert, which I assume we can't, then I agree that we should document this both as a Known Issue and in the Administration Guide. We should note the RHEL version as well as the package version where this change happens. If we don't force customers to update to the latest versions, we'll need to document the previous and current behaviour in the Admin Guide. So we need not mention the samba version since the users would have already updated to 3.3 RHGS before looking at this section. The changes looks good. looks good to me. Marking it verified. Fixed in RHGS 3.3 documentation. |