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

User resource in AIX does not update attributes

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 4.8.0, PUP 4.9.0, PUP 4.10.1
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Environment:

      AIX 7.1 with Puppet 4.x

    • CS Priority:
      Minor
    • CS Frequency:
      1 - 1-5% of Customers
    • CS Severity:
      3 - Serious
    • CS Business Value:
      4 - $$$$$
    • CS Impact:
      For AIX customers who use the user attribute this is very frustrating and requires them to workaround it via exec.
    • QA Risk Assessment:
      Needs Assessment

      Description

      This is a bug specific to AIX. Updating user attributes with the User resource does not actually update the resources when there is more than one attribute defined.

      Example

      Note that the lsuser output is truncated for readability.

      # lsuser testuser
      testuser ... minage=0 maxage=1 ...
       
      # cat testuser.pp
      user { 'testuser':
      ensure => present,
      attributes => [ 'minage=0', 'maxage=5', 'SYSTEM=compat'],
      }
       
      # puppet apply testuser.pp
      Notice: Compiled catalog for pe-aix-71-support.delivery.puppetlabs.net in environment production in 0.11 seconds
      Notice: /Stage[main]/Main/User[testuser]/attributes: attributes changed 'SYSTEM=compat' to 'SYSTEM=compat minage=0 maxage=5'
      Notice: Applied catalog in 0.32 seconds
       
      # lsuser testuser
      testuser ... minage=0 maxage=1 ...
      

      The output of the puppet run indicates that the attributes have been updated despite not changing it on the system. Subsequent runs will show the same result as the attributes have not been updated. The user resource does not detect these attributes.

      # puppet resource user testuser
      user { 'testuser':
        ensure           => 'present',
        attributes       => {'SYSTEM' => 'compat', 'account_locked' => 'false', 'admin' => 'false', 'auth1' => 'SYSTEM', 'auth2' => 'NONE', 'core' => '2097151', 'cpu' => '-1', 'daemon' => 'true', 'data' => '262144', 'fsize' => '2097151', 'histexpire' => '0', 'histsize' => '0', 'login' => 'true', 'loginretries' => '0', 'maxexpired' => '-1', 'maxrepeats' => '8', 'minalpha' => '0', 'mindiff' => '0', 'mindigit' => '0', 'minlen' => '0', 'minloweralpha' => '0', 'minother' => '0', 'minspecialchar' => '0', 'minupperalpha' => '0', 'name' => 'testuser', 'nofiles' => '2000', 'pwdwarntime' => '0', 'registry' => 'files', 'rlogin' => 'true', 'rss' => '65536', 'stack' => '65536', 'su' => 'true', 'sugroups' => 'ALL', 'tpath' => 'nosak', 'ttys' => 'ALL', 'umask' => '22'},
        gid              => '1',
        groups           => ['staff'],
        home             => '/home/testuser',
        password_max_age => '1',
        password_min_age => '0',
        shell            => '/usr/bin/ksh',
        uid              => '207',
      }
      

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support