Bug #6693
Windows Error message: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: Could not find a default provider for user
| Status: | Duplicate | Start date: | 03/13/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | windows | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | https://github.com/jamtur01/puppet/tree/tickets/master/6693 | ||
| Keywords: | Windows 2003 64bit, Windows 2008, Puppet | |||
| Votes: | 0 |
Description
Please see Test Case 1 and 2 for detail steps at puppet windows support wiki page to reproduce this error.
Related issues
History
Updated by Jay Flowers about 1 year ago
I experience the very same behavior as detailed for Windows 2008 on 64bit Vista.
Updated by Markus Roberts about 1 year ago
The problem (as mentioned on the linked page) is that there is presently not a user/group provider for MS Windows. The provider which had been initially proposed required additional tooling on top of the base MS Windows installation (and apparently would have required an additional license for each node!).
If anyone has knowledge of standard, out-of-the-box non-GUI tooling for managing users & groups on MS Windows (e,g, command line utilities for adding, deleting users, etc. that aren’t horribly MS-windows-version dependent) that would help move this forward.
Updated by Markus Roberts about 1 year ago
- Status changed from Unreviewed to Accepted
Updated by William Van Hevelingen about 1 year ago
- Category set to windows
The two commands net user and net group can do basic user and group management. We also need some sort of Active Directory provider for managing domain users and groups.
Updated by T.J. Yang about 1 year ago
This URL looks promising, from googling.
http://stackoverflow.com/questions/383390/create-local-user-with-powershell-windows-vista
Updated by Patrick Mohr about 1 year ago
William Van Hevelingen wrote:
The two commands
net userandnet groupcan do basic user and group management. We also need some sort of Active Directory provider for managing domain users and groups.
According to this article, using those commands to delete can cause problems: http://support.microsoft.com/kb/947215
Quoted from that page:
This issue may occur if the user profile was manually deleted by using the command prompt or by using Windows Explorer. A profile that is manually deleted does not remove the security identifier (SID) from the profile list in the registry. WARNING: Microsoft recommends AGAINST making this the standard way of removing user profiles from machines. The documented and supported approach is using the Advanced System Settings in the system properties, “User Profiles” settings. For applications, this facility is available using the “DeleteProfile” API.
Updated by James Turnbull about 1 year ago
- Status changed from Accepted to In Topic Branch Pending Review
- Affected Puppet version set to 2.7.0rc3
- Branch set to https://github.com/jamtur01/puppet/tree/tickets/master/6693
Example branch that’s a little further along now.
Now getting:
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/posix.rb:23:in `send' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/posix.rb:23:in `get_posix_field' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/posix.rb:103:in `gid' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/group.rb:54:in `insync?' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/group.rb:50:in `each' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/group.rb:50:in `insync?' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/property.rb:162:in `safe_insync?' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:61:in `perform_changes' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in `each' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in `perform_changes' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:133:in `evaluate' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:49:in `apply' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:84:in `eval_resource' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:107:in `evaluate' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:430:in `thinmark' C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:429:in `thinmark' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:107:in `evaluate' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:307:in `traverse' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:141:in `apply' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:632:in `use' C:/Ruby187/lib/ruby/1.8/sync.rb:230:in `synchronize' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:615:in `use' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/master.rb:217:in `setup' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:305:in `run' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:411:in `hook' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:305:in `run' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:402:in `exit_on_fail' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:305:in `run' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:62:in `execute' C:/Ruby187/bin/puppet:4 ←[1;35merr: /File[C:/Windows/puppet/var/log]: Could not evaluate: undefined method `gid' for nil:NilClass←[0m
Which I suspect is because some things are still hard-coded for Posix.
Updated by Josh Cooper 7 months ago
- Affected Puppet version deleted (
2.7.0rc3)
Updated by James Turnbull 7 months ago
- Status changed from In Topic Branch Pending Review to Duplicate