none
Kubernetes node is going down. RRS feed

  • Question

  • {
    "authorization": {
    "action": "Microsoft.Compute/virtualMachines/write",
    "scope": "/subscriptions/x/resourceGroups/x-kubernetes-prod/providers/Microsoft.Compute/virtualMachines/k8s-agent-5d984ae7-0"
    },
    "channels": "Operation",
    "claims": {
    "aud": "https://management.core.windows.net/",
    "iss": "https://sts.windows.net/x/",
    "iat": "1510152637",
    "nbf": "1510152637",
    "exp": "1510156537",
    "aio": "x",
    "appid": "x",
    "appidacr": "1",
    "http://schemas.microsoft.com/identity/claims/identityprovider": "https://sts.windows.net/x/",
    "http://schemas.microsoft.com/identity/claims/objectidentifier": "x",
    "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier": "x",
    "http://schemas.microsoft.com/identity/claims/tenantid": "x",
    "uti": "Ilgo0a6-7EyQBt3PJKUKAA",
    "ver": "1.0"
    },
    "correlationId": "x",
    "eventDataId": "2b608007-9591-47fd-8112-53a3bc39c980",
    "eventName": {
    "value": "EndRequest",
    "localizedValue": "End request"
    },
    "category": {
    "value": "Administrative",
    "localizedValue": "Administrative"
    },
    "eventTimestamp": "2017-11-08T15:30:54.9013935Z",
    "id": "/subscriptions/x/resourcegroups/kubernetes-prod/providers/Microsoft.Compute/virtualMachines/k8s-agent-5d984ae7-0/events/2b608007-9591-47fd-8112-53a3bc39c980/ticks/636457518549013935",
    "level": "Error",
    "operationId": "5bf1458d-86f7-4ca2-bb69-173b3b265915",
    "operationName": {
    "value": "Microsoft.Compute/virtualMachines/write",
    "localizedValue": "Microsoft.Compute/virtualMachines/write"
    },
    "resourceGroupName": "x-kubernetes-prod",
    "resourceProviderName": {
    "value": "Microsoft.Compute",
    "localizedValue": "Microsoft.Compute"
    },
    "resourceType": {
    "value": "Microsoft.Compute/virtualMachines",
    "localizedValue": "Microsoft.Compute/virtualMachines"
    },
    "resourceId": "/subscriptions/x/resourcegroups/x-kubernetes-prod/providers/Microsoft.Compute/virtualMachines/k8s-agent-5d984ae7-0",
    "status": {
    "value": "Failed",
    "localizedValue": "Failed"
    },
    "subStatus": {
    "value": "",
    "localizedValue": ""
    },
    "submissionTimestamp": "2017-11-08T15:31:09.9069663Z",
    "subscriptionId": "x",
    "properties": {
    "statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"DiskBlobAlreadyInUseByAnotherDisk\",\"message\":\"Blob https://00q5hnj66ojwt4wagnt0.blob.core.windows.net/vhds/x-prodmgmt-dynamic-pvc-9692129c-a68c-11e7-9e95-000d3ab41ff4.vhd is already in use by another disk belonging to VM 'k8s-agent-5D984AE7-2'. You can examine the blob metadata for the disk reference information.\"}]}}"
    },
    "relatedEvents": []

    }

    It seems like the disk is used by a previous agent when I scale up the agents in the cluster with the container service interface on azure portal. But only sometimes. How is that possible?

    Deleted the agent 2 to get it up and running again.




    • Edited by Spjutbjorn Thursday, November 9, 2017 12:31 PM
    Thursday, November 9, 2017 12:28 PM

All replies