Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7663

User resource expiry incorrect on SLES 11

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: PUP 4.10.1
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Environment:

      SLES 11 with Puppet 4.x

    • Template:
    • Acceptance Criteria:
      Hide

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

      Show
      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

      Description

      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',
      }
      

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                jarret.lavallee Jarret Lavallee
              • Votes:
                3 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: