2017-06-02 1 views
0

Je tente de provisionner un cluster Azure ACS Kubernetes à l'aide de noeuds Windows. L'interface de ligne de commande Azure 2.0 a bien fonctionné lors de la création d'un cluster Linux, mais elle a échoué lors de la création d'un cluster Windows.Provisionnement du cluster Azure Kubernetes ACS avec Azure 2.0 CLI

Voici la commande que j'exécutais:

***@DAVEPC:~$ az acs create -n RMA-KB-01 -d rmakb -g RG-KB-01 --generate-ssh-keys --orchestrator-type kubernetes --windows --admin-password=***** 

Ceci est l'erreur:

At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details. { "status": "Failed", "error": { 
    "code": "ResourceDeploymentFailure", 
    "message": "The resource operation completed with terminal provisioning state 'Failed'.", 
    "details": [ 
     { 
     "code": "ProvisioningFailed", 
     "message": "Provisioning of resource(s) for container service 'RMA-KB-01' in resource group 'RG-KB-01' failed with errors: Resource type: Microsoft.Compute/virtualMachines, name: 1E4FCacs9001, id: /subscriptions/64b38e64-5dbd-438d-84d3-94e87b553a51/resourceGroups/RG-KB-01/providers/Microsoft.Compute/virtualMachines/1E4FCacs9001, StatusCode: NotFound, StatusMessage: \\n {\r\n \"error\": {\r\n \"code\": \"ImageNotFound\",\r\n \"target\": \"imageReference\",\r\n \"message\": \"The platform image 'MicrosoftWindowsServer:WindowsServer:2016-Datacenter-with-Containers:2016.0.20170127' is not available. Verify that all fields in the storage profile are correct.\"\r\n }\r\n}\r\nResource type: Microsoft.Compute/virtualMachines, name: 1E4FCacs9000, id: /subscriptions/64b38e64-5dbd-438d-84d3-94e87b553a51/resourceGroups/RG-KB-01/providers/Microsoft.Compute/virtualMachines/1E4FCacs9000, StatusCode: NotFound, StatusMessage: \\n {\r\n \"error\": {\r\n \"code\": \"ImageNotFound\",\r\n \"target\": \"imageReference\",\r\n \"message\": \"The platform image 'MicrosoftWindowsServer:WindowsServer:2016-Datacenter-with-Containers:2016.0.20170127' is not available. Verify that all fields in the storage profile are correct.\"\r\n }\r\n}\r\nResource type: Microsoft.Compute/virtualMachines, name: 1E4FCacs9002, id: /subscriptions/64b38e64-5dbd-438d-84d3-94e87b553a51/resourceGroups/RG-KB-01/providers/Microsoft.Compute/virtualMachines/1E4FCacs9002, StatusCode: NotFound, StatusMessage: \\n {\r\n \"error\": {\r\n \"code\": \"ImageNotFound\",\r\n \"target\": \"imageReference\",\r\n \"message\": \"The platform image 'MicrosoftWindowsServer:WindowsServer:2016-Datacenter-with-Containers:2016.0.20170127' is not available. Verify that all fields in the storage profile are correct.\"\r\n }\r\n}\r\n" 
     } 
    ] } } Correlation ID: c69bc7a4-2d0a-431b-ac7e-f98894110eea 

Je viens aussi essayé ce processus en utilisant le portail Azure et obtenu la même erreur. L'aperçu de Windows Container Kubernetes est-il buggé?

Répondre

1

Il semble que son un bug, il n'y a pas l'image VM:

C:\> Get-AzureRmVMImage -Location westeurope -PublisherName $pubName -Offer $offerName ` 
     -Skus 2016-Datacenter-with-Containers | select version 

Version 
------- 
2016.127.20170406 
2016.127.20170411 
2016.127.20170510 

J'ai reproduit votre erreur. Vous devez soulever un problème here.

+0

Problème créé, bien que je ne pense pas que ce soit spécifique à la CLI: https://github.com/Azure/azure-cli/issues/3594 –

+0

Je rencontre le même problème dans Eastus. – Mike