Issue #1583 has been reported by ross.

----------------------------------------
Bug #1583: Groups not recognised when group enumeration turned off
http://projects.reductivelabs.com/issues/show/1583

Author: ross
Status: Unreviewed
Priority: Normal
Assigned to: 
Category: group
Target version: 
Complexity: Unknown
Affected version: 0.24.5
Keywords: winbind samba groups group enum enumeration getgrent libnss nsswitch


When groups are not enumerable using the getgrent function puppet refuses to 
acknowledge a groups existence, erroring with "Could not find group". This 
makes it impossible to set file ownership to a group that isn't returned via a 
call to getgrent.

The problem comes to light when using winbind with the "winbind enum groups" 
option turned off, which is necesary in a large domain due to the huge number 
of groups returned by this call (it can take minutes to complete).

This problem does not affect users, only groups - I also have user enumeration 
disabled but can still use reference those users within puppet.

To reproduce:
1) Turn off group enumeration (exact method tends to be libnss plugin 
dependent, only tested with winbind, although suspect problem will exist 
whenever enumeration is disabled). In winbind this can be done by including the 
line "winbind enum groups = no" in smb.conf.
2) Try and apply the following recipe: file {"/tmp/test": group => 
adsourcedgroup }


----------------------------------------
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to