Jira (PUP-7049) Arista user provider cannot determine a user is absent

[Moses Mendoza (JIRA)]

Title: Message Title

Moses Mendoza created an issue   Puppet / PUP-7049 Arista user provider cannot determine a user is absent Issue Type: Bug Assignee: Unassigned Created: 2016/12/27 11:06 AM Priority: Normal Reporter: Moses Mendoza 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) Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.