Common Pitfalls When Running Custom Recipes on a VS

There are two common pitfalls that may occur when you run custom recipes on a VS. 

Issue 1

VS reboot fails with the Fatal: closed stream error message.

This usually happens when the VS is rebooted as part of a recipe.

Resolution

1. Ensure the task is marked as completed in the OnApp interface via Control Panel's Logs menu.

2. Schedule a reboot on a timer using the following command:

shutdown -r +1 &
exit 0

Issue 2

Another common pitfall is that the VS will not boot after running a custom recipe.

This is usually due to an unsupported kernel and this can happen when running update commands in a recipe.

Resolution

To resolve the issue, refer to the article entitled VM won't boot after I updated kernel.