Issue #1360 has been reported by nwp.
----------------------------------------
Bug #1360: Fix for #1207 breaks allowdupe for groups
http://reductivelabs.com/redmine/issues/show/1360
Author: nwp
Status: Unreviewed
Priority: Normal
Assigned to:
Category:
Target version:
Keywords:
Complexity: Unknown
Patch: None
Affected version: 0.24.4
Take all the following as applying to systems with usermod/groupmod behaving as
mentioned for Solaris in #1207 (Debian behaves this way too, at least -- I
suspect other Linuxes do too).
The fix for ticket #1207 has broken allowdupe for groups.
-o must be specified when and only when:
* you are using usermod to modify a user, and are specifying a UID
* you are using groupmod to modify a group, and are specifying a GID
I think this means that the individual useradd and groupadd providers should
override the modifycmd method provided by provider/nameservice/objectadd.rb -
unless you want to hack that method to identify what it's being inherited by
(ugh!).
I suspect (although I'm not about to check) that specifying allowdupe as
follows:
<pre>
user { "nwp":
ensure => present,
allowdupe => true,
}
</pre>
(or similarly for a group) without specifying an id will also break, as it will
be specifying "-o" without specifying a UID/GID for the object being modified.
Cheers,
Nick
----------------------------------------
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
-~----------~----~----~----~------~----~------~--~---
