Issue #13078 has been updated by Daniel Pittman.
Patrick Carlisle wrote: > I think it's unlikely that we'll change this, but it seems a reasonable use > case. Specifically, Nigel, can you let us know if there is a specifically desired behaviour from your point of view? My feeling is that we should treat "the gid is out of sync" as a reason to change the gid *and no other properties* of the group by name. That is, the name of the group is the primary attribute, alone, and the gid is just another facet to change. We shouldn't do anything about files on disk that had the old gid; if folks want that changed too, they can engineer that themselves. ---------------------------------------- Bug #13078: Renaming a group fails: "groupadd: GID already exists" https://projects.puppetlabs.com/issues/13078#change-56847 Author: Bill Tong Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: Keywords: Branch: group { 'originally-old': ensure => present, gid => 5, name => 'newname', } fails with GID already exists. -- 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://projects.puppetlabs.com/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.
