Packer skips to next provisioner after 180s

[dgt...@gmail.com]

Hi,

I am trying to install a large application which takes around 20 minutes. 

The powershell script that installs the application uses a Wait-Process $process.id to make sure the script doesn't exit before finalizing the install. 

The process is still running after 3 minutes, but packer still skips to the next provisioner

Any idea  what is causing this?

2019/02/22 11:38:53 ui: amazon-ebs: Run install task .

2019/02/22 11:39:03 ui: amazon-ebs: Deploy-Application.exe started .

2019/02/22 11:42:03 packer: 2019/02/22 11:42:03 [INFO] command 'powershell -executionpolicy bypass "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-5c6fcc2e-3bd6-2c19-f0a6-63a60c0ef939.ps1; &'c:/Windows/Temp/script-5c6fcc2e-184c-6bea-fae9-f105b1d545af.ps1'; exit $LastExitCode }"' exited with code: 0

2019/02/22 11:42:03 packer: 2019/02/22 11:42:03 [INFO] RPC endpoint: Communicator ended with: 0

2019/02/22 11:42:03 [INFO] 659837 bytes written for 'stdout'

2019/02/22 11:42:03 [INFO] 0 bytes written for 'stderr'

2019/02/22 11:42:03 [INFO] RPC client: Communicator ended with: 0

2019/02/22 11:42:03 [INFO] RPC endpoint: Communicator ended with: 0

2019/02/22 11:42:03 packer: 2019/02/22 11:42:03 [INFO] 659837 bytes written for 'stdout'

2019/02/22 11:42:03 packer: 2019/02/22 11:42:03 [INFO] 0 bytes written for 'stderr'

2019/02/22 11:42:03 [INFO] (telemetry) ending powershell

2019/02/22 11:42:03 [INFO] (telemetry) Starting provisioner powershell

2019/02/22 11:42:03 packer: 2019/02/22 11:42:03 [INFO] RPC client: Communicator ended with: 0

2019/02/22 11:42:03 ui: ask: ==> amazon-ebs: Pausing before the next provisioner . Press enter to continue.