[PUP-9562] User resource does not respect forcelocal for the comment parameter Created: 2019/03/14 Updated: 2019/11/18 Resolved: 2019/11/06
|Component/s:||Types and Providers|
|Affects Version/s:||PUP 5.5.10|
|Fix Version/s:||PUP 6.11.0|
|Reporter:||Jarret Lavallee||Assignee:||Gabriel Nagy|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Puppet 5.5.x with LDAP configured on EL 5.x
|Template:||PUP Bug Template customfield_10700 300292|
|Sprint:||NW - 2019-10-16, NW - 2019-10-30, NW - 2019-11-13|
|Method Found:||Customer Feedback|
|Release Notes:||Bug Fix|
|Release Notes Summary:|| Prior to this fix, a user resource configured with forcelocal would still try to sync the comment with the external directory services, meaning that subsequent Puppet runs would not be idempotent.
To fix this, we compare the `in_sync` with the contents of the local `/etc/passwd` file.
A user resource configured with forcelocal will still try to sync the comment with the external directory services. It does use the `lusermod` to modify the local `/etc/passwd` to the comment specified in the user resource, but it compares the `in_sync` with the external directory services, meaning that it always updates the comment on catalog compilation.
4. Apply the following manifest on the agent multiple times and observe that it tries to update the comment every time.