[PUP-7663] User resource expiry incorrect on SLES 11 Created: 2017/06/14  Updated: 2018/05/21

Status: Accepted
Project: Puppet
Component/s: Types and Providers
Affects Version/s: PUP 4.10.1
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Jarret Lavallee Assignee: Unassigned
Resolution: Unresolved Votes: 3
Labels: sles, type_and_provider, user
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

SLES 11 with Puppet 4.x

Acceptance Criteria:

The expiry attribute should configure the user's expiry to `never` in SLES 11

Team: Platform OS
Method Found: Customer Feedback
CS Priority: Reviewed
QA Risk Assessment: Needs Assessment


Setting the user resource's expiry to `absent` in SLES 11 results in the expiry for the user to be `1970-01-01` instead of `never`. This is different from what is seen in CentOS 6/7, and results in users that are not able to authenticate.

# puppet resource user testuser ensure=present expiry=absent
Notice: /User[testuser]/ensure: created
user { 'testuser':
  ensure => 'present',
  expiry => '1970-01-01',
# puppet resource user testuser ensure=present expiry=absent
Notice: /User[testuser]/expiry: undefined 'expiry' from '1970-01-01'
user { 'testuser':
  ensure => 'present',
  expiry => '1970-01-01',

Generated at Wed Nov 20 22:33:11 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.