Bug 1499025

Summary: samba-3.6.23-45.el6_9:0.x86_64 breaks directory listing
Product: Red Hat Enterprise Linux 6 Reporter: aheverle
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9CC: asn, cobrown, gdeschner, jarrpa
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-19 14:08:34 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 aheverle 2017-10-05 20:47:23 UTC 
Description of problem:

Since installing samba-3.6.23-45.el6_9:0.x86_64, users can no longuer see files inside shared directories. The listing works at the topmost part of the share, but as soon as you dig down one level of directory, the files inside aren't visible anymore.

Please see these 2 very short links. This is 2 people reporting the same problem:
https://www.centos.org/forums/viewtopic.php?t=64334
http://samba.2283325.n4.nabble.com/problems-with-samba-shares-td4724556.html

The workaround for the moment seems to be yum downgrade to the last known working version, which is 3.6.23-44.el6_9. For it to work for myself, i've had to  go to version 3.6.23-43.el6_9 because i do not have version 3.6.23-44.el6_9 in my cloned channel on my satellite server.

So the cmd below effectively restored the functionality for me:
# yum downgrade samba-winbind-3.6.23-43.el6_9.x86_64 samba-winbind-clients-3.6.23-43.el6_9.x86_64 samba-3.6.23-43.el6_9.x86_64 samba-common-3.6.23
-43.el6_9.x86_64 samba-client-3.6.23-43.el6_9.x86_64

Version-Release number of selected component (if applicable):
samba-3.6.23-45.el6_9

How reproducible:
Everytime
Comment 3 Andreas Schneider 2017-10-19 14:08:34 UTC 

*** This bug has been marked as a duplicate of bug 1495148 ***