On Wednesday, July 17, 2013 11:33:51 AM UTC-7, Josh D wrote: > > > > On Wednesday, July 17, 2013 10:39:51 AM UTC-6, Josh Cooper wrote: >> >> >> Based on http://www.python.org/download/releases/2.5/msi/ I think python >> is only being installed for the current user, not all users. You'll have to >> specify ALLUSERS=1 to get that behavior. I don't see this explicitly called >> out in our docs >> http://docs.puppetlabs.com/windows/writing.html#packagepackage but it >> should be. Could you file a ticket? >> >> > Ok, I changed the rule to: > package { 'Python 2.7.5 (64-bit)': > ensure => installed, > source => > '\\<server>\<share>\Tools\Puppet\win64\Python\python-2.7.5.amd64.msi', > install_options => [{ 'TARGETDIR' => 'C:\Python27' }, {'ALLUSERS' => > '1' }], > require => [Package['MinGW-W64 version 4.5.3'], > Package['Cygwin version 1.7.15']], > } > > > I also removed the existing install, so Python is not on my machine. > After restarting the service, I got the same exact error and stack trace. > I verified that ALLUSERS=1 was passed in. > > Puppet - Information 1 > Executing 'msiexec.exe /qn /norestart /i > \\<server>\<share>\Python\python-2.7.5.amd64.msi TARGETDIR=C:\Python27 > ALLUSERS=1' > > > Puppet - Error 3 > Failed to install: Fail on INT 24. > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/provider/package/windows.rb:99:in > `check_result' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/provider/package/windows.rb:64:in `install' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/type/package.rb:67:in `block (3 levels) in > <module:Puppet>' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/property.rb:197:in `call_valuemethod' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/property.rb:498:in `set' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/property.rb:581:in `sync' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:114:in > `apply_parameter' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:56:in > `perform_changes' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:139:in > `evaluate' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction.rb:48:in `apply' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction.rb:83:in `eval_resource' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction.rb:103:in `block (2 levels) in > evaluate' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:351:in > `block in thinmark' > C:/Program Files (x86)/Puppet > Labs/Puppet/sys/ruby/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:350:in > `thinmark' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction.rb:103:in `block in evaluate' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction.rb:382:in `traverse' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/transaction.rb:98:in `evaluate' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/resource/catalog.rb:146:in `apply' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/configurer.rb:122:in `block in apply_catalog' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:179:in > `block in benchmark' > C:/Program Files (x86)/Puppet > Labs/Puppet/sys/ruby/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:178:in > `benchmark' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/configurer.rb:121:in `apply_catalog' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/configurer.rb:179:in `run' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in > `block (5 levels) in run' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/agent/locker.rb:20:in `lock' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in > `block (4 levels) in run' > C:/Program Files (x86)/Puppet > Labs/Puppet/sys/ruby/lib/ruby/1.9.1/sync.rb:227:in `sync_synchronize' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in > `block (3 levels) in run' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/agent.rb:119:in `with_client' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:42:in > `block (2 levels) in run' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:84:in > `run_in_fork' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:41:in > `block in run' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application.rb:179:in `call' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application.rb:179:in `controlled_run' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:39:in > `run' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application/agent.rb:353:in `onetime' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application/agent.rb:327:in `run_command' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application.rb:364:in `block (2 levels) in > run' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application.rb:456:in `plugin_hook' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application.rb:364:in `block in run' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:504:in > `exit_on_fail' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/application.rb:364:in `run' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/util/command_line.rb:132:in `run' > C:/Program Files (x86)/Puppet > Labs/Puppet/puppet/lib/puppet/util/command_line.rb:86:in `execute' > C:/Program Files (x86)/Puppet Labs/Puppet/puppet/bin/puppet:4:in `<main>' >
Are you sure that puppet when running as LocalSystem has permission to access the share[1]? Can puppet running as LocalSystem install the package from a local filesystem? Another user had to modify the NTFS and Share permissions for 'Domain Computers' to access the share (map the drive)[2]. This is because LocalSystem doesn't have any credentials with which to access the network. Josh [1] https://groups.google.com/d/msg/puppet-users/86dBOxvirK0/I6CtTH_BGEgJ [2] https://groups.google.com/d/topic/puppet-users/xoJpt6ARe0Y/discussion -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
