Linux worker instance fail to deploy if deadline is not configured as daemon

[yashda]

The worker AMI will not get deployed successfully if deadline launcher is configured to run as standalone service.
This is because when worker is not configure to run as service, it starts the launcher with command .../deadlinelauncher -nogui. This is a blocking command and wont exit until the launcher stops. Because of this, the instance will never be able to send success signal and the instance cloudformation deployment will timeout waiting for the signal.

"$DEADLINE_LAUNCHER" -nogui

should be changed to

"$DEADLINE_LAUNCHER" -nogui &

Reproduction Steps

Create a worker AMI by installing deadline client as standalone process (not a daemon).
Sample installation command:

DeadlineClientInstaller.run --launcherdaemon false

Use this AMI to deploy a worker instance fleet. The deployment should fail stating Failed to receive 1 resource signal(s) for the current batch. Each resource signal timeout is counted as a FAILURE.

Error Log

Environment

• OS : Linux

---

This is 🐛 Bug Report