计划工作的延迟导致他们得到备份和失败 [英] Delay in Scheduled Jobs Caused Them to Get Backed Up and Fail

问题描述

我有一个自动化作业，每15分钟运行一次，以停止正在运行的VM并启动资源组中的下一个VM。

I注意到计划的工作在UTC时间3月19日晚上10:30开始延迟。这项工作需要将近45分钟才能完成（通常需要2-3分钟），从而推迟了未来的工作。看起来这些工作最终赶上了UTC时间上午3点1点，但到那时由于之前的延迟，
工作不再有效。现在所有VM都已停止并显示错误"Provisioning failed"。未知的网络分配错误.. NetworkingInternalOperationError"

解决方案

您好Jjohnsondev，抱歉服务中断，我同意更新脚本会阻止这个问题的未来发生。要确定rootcause，我们需要使用

这些步骤。

如果您没有支持计划，请发送邮件至AzCommunity @ microsoft .com，包括您的订阅ID和此MSDN线程的链接（用于上下文），我们将协助您使用Azure支持。

干杯，

I have an automation job that runs every 15 minutes to stop the running VM and start the next VM in a resource group.

I noticed the scheduled jobs started to get delayed on 3/19 10:30PM UTC. This job took nearly 45 minutes to complete (usually takes 2-3 minutes) which in turn delayed future jobs. It looks like the jobs finally caught up on 3/20 1:00AM UTC, but by then the jobs were no longer working due to the previous delays. All VMs are now stopped and display the errors "Provisioning failed. Unknown network allocation error.. NetworkingInternalOperationError"

解决方案

Hi Jjohnsondev, sorry for the service disruption and I do agree that updating the script will prevent future occurrence of this issue. To determine rootcause, we will need to engage the Azure technical support team using these steps.

If you do not have a support plan, please send mail to [e-mail], include your subscription ID and a link to this MSDN thread (for context) and we will assist you with engaging Azure support.

Cheers,

这篇关于计划工作的延迟导致他们得到备份和失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！