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

Arista user provider cannot determine a user is absent

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: PUP 4.8.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Agent
    • QA Risk Assessment:
      Needs Assessment

      Description

      In debugging a test failure related to PUP-6777, I discovered strange behavior from puppet on our Arista test hosts. It appears that puppet cannot tell that a user does not exist - or, conversely, thinks any user you supply exists:

       

      -bash-4.1# puppet resource user foo75181
      user

      { 'foo75181': ensure => 'present', comment => 'Unknown User (foo75181)', gid => '88', home => '/home/foo75181', shell => '/usr/bin/RunCli', uid => '102341648', }

      -bash-4.1# puppet resource user foobar
      user

      { 'foobar': ensure => 'present', comment => 'Unknown User (foobar)', gid => '88', home => '/home/foobar', shell => '/usr/bin/RunCli', uid => '43894025', }

      -bash-4.1# puppet resource user foobazbarqux
      user

      { 'foobazbarqux': ensure => 'present', comment => 'Unknown User (foobazbarqux)', gid => '88', home => '/home/foobazbarqux', shell => '/usr/bin/RunCli', uid => '97032648', }

      None of these are actually users on the system. For PUP-6777, this means that rather than run `useradd` to create a user with a comment, on arista puppet is running `usermod` (as if the user already existed)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              moses Moses Mendoza
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support