Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)

[Rob Reynolds (JIRA)]

Title: Message Title

Rob Reynolds commented on an issue   Re: Upgrade win32-taskscheduler (or replace) Trying to create a task though: C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:117:in `block in UseInstance' C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:114:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:114:in `new' C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:114:in `UseInstance' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:527:in `block (2 levels) in new_work_item' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:522:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:522:in `new' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:522:in `block in new_work_item' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:516:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:516:in `new' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:516:in `new_work_item' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:187:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:212:in `new' C:/code/puppetlabs/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:212:in `create' C:/code/puppetlabs/puppet/lib/puppet/property/ensure.rb:16:in `block in defaultvalues' C:/code/puppetlabs/puppet/lib/puppet/property.rb:197:in `call_valuemethod' C:/code/puppetlabs/puppet/lib/puppet/property.rb:498:in `set' C:/code/puppetlabs/puppet/lib/puppet/property.rb:581:in `sync' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:204:in `sync' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:128:in `sync_if_needed' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:81:in `perform_changes' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:20:in `evaluate' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:203:in `apply' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:216:in `eval_resource' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:146:in `call' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:146:in `block (2 levels) in evaluate' C:/code/puppetlabs/puppet/lib/puppet/util.rb:327:in `block in thinmark' C:/ruby193/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/code/puppetlabs/puppet/lib/puppet/util.rb:326:in `thinmark' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:146:in `block in evaluate' C:/code/puppetlabs/puppet/lib/puppet/graph/relationship_graph.rb:118:in `traverse' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:137:in `evaluate' C:/code/puppetlabs/puppet/lib/puppet/resource/catalog.rb:167:in `block in apply' C:/code/puppetlabs/puppet/lib/puppet/util/log.rb:149:in `with_destination' C:/code/puppetlabs/puppet/lib/puppet/transaction/report.rb:112:in `as_logging_destination' C:/code/puppetlabs/puppet/lib/puppet/resource/catalog.rb:166:in `apply' C:/code/puppetlabs/puppet/lib/puppet/configurer.rb:117:in `block in apply_catalog' C:/code/puppetlabs/puppet/lib/puppet/util.rb:161:in `block in benchmark' C:/ruby193/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/code/puppetlabs/puppet/lib/puppet/util.rb:160:in `benchmark' C:/code/puppetlabs/puppet/lib/puppet/configurer.rb:116:in `apply_catalog' C:/code/puppetlabs/puppet/lib/puppet/configurer.rb:198:in `run' C:/code/puppetlabs/puppet/lib/puppet/application/apply.rb:295:in `apply_catalog' C:/code/puppetlabs/puppet/lib/puppet/application/apply.rb:229:in `block in main' C:/code/puppetlabs/puppet/lib/puppet/context.rb:64:in `override' C:/code/puppetlabs/puppet/lib/puppet.rb:237:in `override' C:/code/puppetlabs/puppet/lib/puppet/application/apply.rb:191:in `main' C:/code/puppetlabs/puppet/lib/puppet/application/apply.rb:152:in `run_command' C:/code/puppetlabs/puppet/lib/puppet/application.rb:384:in `block (2 levels) in run' C:/code/puppetlabs/puppet/lib/puppet/application.rb:510:in `plugin_hook' C:/code/puppetlabs/puppet/lib/puppet/application.rb:384:in `block in run' C:/code/puppetlabs/puppet/lib/puppet/util.rb:479:in `exit_on_fail' C:/code/puppetlabs/puppet/lib/puppet/application.rb:384:in `run' C:/code/puppetlabs/puppet/lib/puppet/util/command_line.rb:146:in `run' C:/code/puppetlabs/puppet/lib/puppet/util/command_line.rb:92:in `execute' C:/code/puppetlabs/puppet/bin/puppet:8:in `<top (required)>' C:/ruby193/lib/ruby/gems/1.9.1/bin/puppet:23:in `load' C:/ruby193/lib/ruby/gems/1.9.1/bin/puppet:23:in `<main>' Error: /Stage[main]/Main/Scheduled_task[Notepad]/ensure: change from absent to present failed: Could not set 'present' on ensure: :pointer argument is not a valid pointer at 41:c:/temp/scheduled_tasks.pp Add Comment   Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.