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

Puppet raises error when trying to apply user resources under FreeBSD

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.6.2
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
    • Environment:

      FreeBSD, Ruby 2.0.0p598

    • Template:

      Description

      Apologies if i filed this issue under the wrong project. I have been working on a problem that could be an issue with "pw" under FreeBSD.

      Puppet manages about 100 user resources and since two weeks some (not all) of my FreeBSDs silently started to raise errors with some (not all) of these resources.

      Every resource has exactly the same structure:

      define myusers($username, $comment, $password, $id, $ensure) {
        user { $username:
          comment => $comment,
          password => $password,
          uid => $id,
          gid => $id,
          managehome => true,
          ensure => $ensure,
        }
      }
       
      class user::joe {
        myuser { "joe":
          username => "joe",
          comment => "Joe Eig",
          password => 'blabla',
          id => 1100,
          ensure => present,
        }
      }
      

      The result is:

      Error: Could not create user joe: Execution of '/usr/sbin/pw useradd joe -d /home/joe -u 1100 -g 1100 -c Joe Eig -m' returned 74: pw: user 'joe' already exists
      Error: /Stage[main]/User::Joe/myuser[joe]/User[joe]/ensure: change from absent to present failed: Could not create user joe: Execution of '/usr/sbin/pw useradd joe -d /home/joe -u 1100 -g 1100 -c Joe Eig -m' returned 74: pw: user 'joe' already exists
      

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                joeig Joe Eig
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support