Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title Josh Cooper commented on PUP-1131 Re: Puppet raises error when trying to set owner to non-existant user Puppet no longer requires that the puppet user exist, so this particular issue has been resolved, and I'm re-closing this. There is a second issue where puppet will raise an exception if there isn't a suitable user provider, filed as PUP-1162. You can see the problem on line 382: https://github.com/puppetlabs/puppet/blob/3.7.5/lib/puppet/type/user.rb#L382 due to provider being nil. We've seen this problem on centos when running as non-root, because useradd isn't world-executable. I imagine something similar is going on with Solaris. Chris Denneen please follow PUP-1162 for updates. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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.
Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title Chris Denneen commented on PUP-1131 Re: Puppet raises error when trying to set owner to non-existant user Installed 3.7.5 on Solaris 2.6 with rubygems. Getting this via trace: bash-2.05# puppet agent -t --noop --verbose --debug --trace Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Failed to load library 'shadow' for feature 'libshadow' Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Puppet::Type::User::ProviderLdap: true value when expecting false Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not exist Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Puppet::Type::User::ProviderLdap: true value when expecting false Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not exist Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist Error: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `exists?' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/type/user.rb:382:in `exists?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:800:in `service_user_available?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `send' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `safe_to_use_settings_value?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:43:in `value' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:106:in `owner' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:160:in `to_resource' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:916:in `to_catalog' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:912:in `each' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:912:in `to_catalog' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:982:in `use' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application/agent.rb:404:in `setup' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:507:in `plugin_hook' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util.rb:488:in `exit_on_fail' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util/command_line.rb:146:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util/command_line.rb:92:in `execute' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/bin/puppet:8 /usr/local/bin/puppet:23:in `load' /usr/local/bin/puppet:23 Error: Could not prepare for execution: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `exists?' for nil:NilClass undefined method `exists?' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/type/user.rb:382:in `exists?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:800:in `service_user_available?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `send' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `safe_to_use_settings_value?'
Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title
Chris Denneen commented on PUP-1131
Re: Puppet raises error when trying to set owner to non-existant user
I've manually added puppet user and group. I've manually added /etc/puppet/puppet.conf, and /var/lib/puppet/ {bucket,clientbucket,lib,log,run,ssl,state,yaml}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title John Duarte updated an issue Puppet / PUP-1131 Puppet raises error when trying to set owner to non-existant user Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title Jason Antman commented on an issue Re: Puppet raises error when trying to set owner to non-existant user The only useful in the Redmine ticket that's directly related to the ticket (puppet creating the puppet user) is over 2 years old, and talking about 0.25 and 2.6. Neither the original reporter nor the person who commented a year ago are watching the Redmine ticket, let alone this one. Given how long it's been since there were updates to this, and that all of those updates are about a now-deprecated (and in fact archaic) version, I'm going to close this Unable to Reproduce. Feel free to reopen if anyone thinks it's still an issue. Add Comment Puppet / PUP-1131 Puppet raises error when trying to set owner to non-existant user When I ran 0.25.5, I relied on the puppet client to create the puppet user. Since I've upgraded to 2.6.1, the puppet user must already exist before the puppet client will run, otherwise the puppet client bails with an error: err: Could not run Puppet configuration client: Could not find user puppet This seems to be a fairly major regression. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title redmine.exporter created an issue Puppet / PUP-1131 Puppet raises error when trying to set owner to non-existant user Issue Type: Bug Assignee: Unassigned Created: 17/Dec/13 5:20 AM Labels: redmine Priority: Normal Reporter: redmine.exporter When I ran 0.25.5, I relied on the puppet client to create the puppet user. Since I've upgraded to 2.6.1, the puppet user must already exist before the puppet client will run, otherwise the puppet client bails with an error: err: Could not run Puppet configuration client: Could not find user puppet This seems to be a fairly major regression. Add Comment
