Azure Batch-Shipyard: create VMs inside a VNET, unusable status

自作多情 提交于 2019-12-11 17:56:14

问题


I am having issues using Azure Batch-Shipyard to create a set of VMs inside a VNET.

Here is my configuration:

  • Storage account (mystorage) allows only access from myvnet/mysubnet: storage and VNET configuration
  • Batch account creates VMs inside this exact same VNET myvnet/mysubnet (using arm_subnet_id)
  • VNET myvnet/mysubnet is associated to Network Security Groups that allows TCP traffic on ports 29876-29877 from any source to any destination as detailed in Batch-Shipyard documentation: NSG rules

Unfortunately, all VMs that are created with this configuration are still in unusable state, even if they get a correct IP adress from myvnet/mysubnet

I also tried many other configuration but nothing is working yet:

  • remove VNET configuration from Batch-Shipyard configuration: VM starts bu start task fails since VM is not inside the VNET and Storage account is inside the VNET
  • remove NSG associated to myvnet/mysubnet: same unusable state

Did a miss something in the Azure configuration? Thanks for your help.

来源:https://stackoverflow.com/questions/50678561/azure-batch-shipyard-create-vms-inside-a-vnet-unusable-status

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!