Azure VM scale sets not accessible and cannot restart

Question

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.

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

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",
    }
}

score 0 · Answer 1 · answered Jan 04 '18 at 13:48

0

Check Network Security Group is blocking outbound connectivity from your VM? VM Agent and Extensions are updated

If HTTPS is blocked to this storage account then you will get this error message. More information here http://www.deployazure.com/compute/virtual-machines/azure-vm-agent-extensions-deep-dive-part-3/

answered Jan 04 '18 at 13:48

SumanthMarigowda-MSFT

1,920
9
14

Thanks, I updated my question with NSG outbound rule. Right now, we just use default outbound rule, so outbound connectivity should work. – Youxu Jan 04 '18 at 18:17

Jason Ye · Answer 2 · 2018-01-08T07:21:27.210

0

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

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:

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.

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

Update:

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.

edited Jan 08 '18 at 07:21

answered Jan 05 '18 at 08:56

Jason Ye

13,710
2
16
25

Thanks Jason! Actually we already have VM in same Vnet as VMSS, we used to use this VM remote to the VMSS instances via Enter-PSSession cmd. But now we are not able to remote to the problematic instances. As restart always failed. What shall I do? – Youxu Jan 05 '18 at 22:10
@Youxu Please try to restart VMSS again, if that does not work for you, please create a support ticket to Azure, sorry for all the inconvenience caused for you. – Jason Ye Jan 08 '18 at 07:22
restart still not work. I have to re-image the VM to bring it back. – Youxu Jan 08 '18 at 23:22

Azure VM scale sets not accessible and cannot restart

2 Answers2

Linked