Azure VM规模集不可访问并且无法重新启动 [英] Azure VM scale sets not accessible and cannot restart

问题描述

今天，我发现我无法远程访问我的Azure VM规模集实例(赢得2016年Nano服务器).然后，我尝试使用powershell重新启动VM规模集实例，但收到以下类似错误消息:

Today, I found I cannot remote into my Azure VM scale set instances (win 2016 Nano Server). I then tried restart the VM scale set instance using powershell but got following like error:

Restart-AzureRmVmss : Long running operation failed with status 'Failed'. Additional Info:'VM 'master-vmss_0' has not
reported status for VM agent or extensions. Please verify the VM has a running VM agent, and can establish outbound
connections to Azure storage.'
ErrorCode: VMAgentStatusCommunicationError
ErrorMessage: VM 'master-vmss_0' has not reported status for VM agent or extensions. Please verify the VM has a
running VM agent, and can establish outbound connections to Azure storage.

我们的VM规模集已经正确运行了将近一年.VMSS发生了什么?Azure最近是否在VMSS上进行了更改?

Our VM scale sets has been running correctly for nearly one year. What happened on VMSS? Did Azure make changes on VMSS recently?

使用NSG出站规则更新:

Update with NSG outbound rule:

{
    "name": "AllowVnetOutBound",
    "properties": {
        "provisioningState": "Succeeded",
        "description": "Allow outbound traffic from all VMs to all VMs in VNET",
        "access": "Allow",
        "priority": 65000,
        "direction": "Outbound",
    }
},
{
    "name": "AllowInternetOutBound",
    "properties": {
        "provisioningState": "Succeeded",
        "description": "Allow outbound traffic from all VMs to Internet",
        "access": "Allow",
        "priority": 65001,
        "direction": "Outbound",
    }
},
{
    "name": "DenyAllOutBound",
    "etag": "W/\"a8e5e396-4f92-4118-b8ea-9b7d0111079f\"",
    "properties": {
        "provisioningState": "Succeeded",
        "description": "Deny all outbound traffic",
        "access": "Deny",
        "priority": 65500,
        "direction": "Outbound",
    }
}

推荐答案

我们的VM规模集已经正确运行了将近一年.什么发生在VMSS上?Azure最近是否在VMSS上进行了更改?

Our VM scale sets has been running correctly for nearly one year. What happened on VMSS? Did Azure make changes on VMSS recently?

最近，Azure中进行了一些维护，将主机操作系统更新为Windows Server2016.我们可以在Azure门户中找到维护信息，如下所示:

Recently, there are some maintenance in Azure, update host OS to windows server 2016. We can find the maintenance information in Azure portal, like this:

在您的情况下，也许我们可以在VMSS的vnet中创建新VM ，然后使用该VM远程运行VMSS实例，以检查VM代理状态.

In your scenario, maybe we can create a new VM in VMSS' vnet, then use that VM to remote the VMSS instance, to check the VM agent status.

如果VM代理状态为关闭，我们应该启动它.

If the VM agent status is down, we should start it.

更新:

最近，您在计划的维护VM重新引导后遇到启动VM故障的问题.这是由于后端中的容器故障问题造成的.
我们的后端工程师已经检查了有问题的租户并采取了缓解措施.您可以尝试重新启动VMss吗?如果这不起作用，请创建支持票证到Azure.

Recently you experienced an issue with starting VM failure after planned maintenance VM reboot. This is due to container fault issue in the backend.
Our backend engineer has checked the faulted tenant and applied mitigation. Can you try to restart the VMss again? If that does not work, please create a support ticket to Azure.

再次对您造成的不便深表歉意.

Again, sorry for all the inconvenience caused for you.

这篇关于Azure VM规模集不可访问并且无法重新启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！