I recently encountered an issue while using the AZHPC script (azhpc-build) on Azure. When the script fails to execute due to some error (for example provisioning failed due to invalid parameter), it still creates resources like VM scale sets, vnets, and others. As a result, users are charged for these resources, even though the script execution was unsuccessful. When checking the Azure portal, it does not show any virtual machines running, which can lead users to believe that they are not being charged. As a result, users may incur unexpected costs due to this issue, which can be frustrating and negatively impact their experience.
Expected behavior:
The azhpc-build script should delete the resources created when it fails to execute completely to avoid unintentional charges to the user. The AZHPC script should not create and charge for resources when it fails to execute.
I recently encountered an issue while using the AZHPC script (
azhpc-build) on Azure. When the script fails to execute due to some error (for exampleprovisioning failed due to invalid parameter), it still creates resources like VM scale sets, vnets, and others. As a result, users are charged for these resources, even though the script execution was unsuccessful. When checking the Azure portal, it does not show any virtual machines running, which can lead users to believe that they are not being charged. As a result, users may incur unexpected costs due to this issue, which can be frustrating and negatively impact their experience.Expected behavior:
The
azhpc-buildscript should delete the resources created when it fails to execute completely to avoid unintentional charges to the user. The AZHPC script should not create and charge for resources when it fails to execute.