This is failing CI because we register a task to run cmd.exe /c puppet agent -t as LocalSystem. On 2008r2 the task scheduler cannot find puppet in its PATH. This is only an issue now, because the test had been skipped until this change. I'm not sure why/how the test is passing on 2019. I am guessing that when the puppet MSI is installed, it modifies the system PATH in a way that the schedule service sees the change, but 2008r2 does not. I think the beaker test used to pass on 2008r2 because C:\Program Files\Puppet Labs\puppet\bin was in the VM's system PATH, but they were last due to the way we use puppet to provision them during imaging. I'm thinking the best thing is to explicitly specify the full path for the scheduled task, something like:
cmd /c "C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" /c agent -t
|
Or setting the current working directory for the task to C:\Program Files\Puppet Labs\Puppet\bin. To reproduce, run
$ bundle exec rake ci:test:aio SERVER_VERSION=6.9.2 SHA=525b88bc94cd2154a863c9d80e46981035f39d60 TESTS=tests/windows/PUP-9719_windows_system_first_pa_run.rb TEST_TARGET=windows2008r2-64a OPTIONS='--preserve-hosts=always
|
|