The native Puppet integration fails with 'Error: failed task "create" after 2 attempt(s)' when the workflow reboots the VM.
Article ID: 379556
Updated On:
Products
Issue/Introduction
When trying to install a sql server with puppet. Multiple configurations are applied, requiring multiple restarts of the VM to ensure each incremental configuration is applied.
Even if VM is not restarted, multiple puppet runs would be required in order for the run command to return with exit code of 0 or 2(0 or 2 exit code is considered a successful puppet run). The command is retried until 'puppetMaxRuns' VCT property is reached.
But when the puppet run does restart a VM, we are unable to retry running the puppet run command since the process id of the script is lost and the script is assumed complete. Customer hence wants a way to retry running the puppet command until is truly returns with exit code of 0 or (or until puppetMaxRuns counter is reached)to ensure all configurations are applied.
Environment
Aria Automation 8.16 & Later
Cause
Currently, we do not save any intermediate state of the script run and resume the script with the state at which the restart happened.
Resolution
This issue is resolved in 8.18.1. Download Link
Feedback
