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

User resource expiry incorrect on SLES 11

    XMLWordPrintable

    Details

    • 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:
      Night's Watch
    • Story Points:
      2
    • Sprint:
      NW - 2020-04-29, NW - 2020-05-13
    • Method Found:
      Customer Feedback
    • CS Priority:
      Reviewed
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      On SLES 11, setting a user resource's expiry to 'absent' results in disabling the user instead of never disabling the user.
      This PR now fixes this bus so that it works as on other platforms.
      Show
      On SLES 11, setting a user resource's expiry to 'absent' results in disabling the user instead of never disabling the user. This PR now fixes this bus so that it works as on other platforms.
    • 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

            People

            Assignee:
            dorin.pleava Dorin Pleava
            Reporter:
            jarret.lavallee Jarret Lavallee
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support