Open git001 opened 11 months ago
Thank you for opening this issue, we will look into it.
Hi @git001 Find similar issue https://github.com/Azure/azure-cli/issues/7700. | ||
---|---|---|
Issue title | VM create should show usage error when --vnet-name and --subnet are used incorrectly |
|
Create time | 2018-10-29 | |
Comment number | 7 |
Possible solution:
The issue is that the --vnet-name
parameter only accepts a vnet name, not an ID. Only --subnet
accepts a name or ID. Therefore, you need to reference the ID of the subnet and remove the reference of vnet. Since referencing the subnet automatically adds the correct vnet.
Please confirm if this resolves your issue.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.
Hi @git001 Find similar issue #7700.
Issue title VM create should show usage error when
--vnet-name
and--subnet
are used incorrectly Create time 2018-10-29 Comment number 7Possible solution: The issue is that the
--vnet-name
parameter only accepts a vnet name, not an ID. Only--subnet
accepts a name or ID. Therefore, you need to reference the ID of the subnet and remove the reference of vnet. Since referencing the subnet automatically adds the correct vnet.Please confirm if this resolves your issue.
Not confirmed
Describe the bug
I tried to create a key vault with
--network-acls
and got the following error.But even the help shows that the syntax should be
/subscriptions/MY_SUBS/resourceGroups/rg-01/spoke-01/snet-01
Is this a misusing from my site or a doc bug? Can I put a vnet from another RG into the
--network-acls
json?Related command
Errors
Issue script & Debug output
Expected behavior
I would expect that the vnets are configured in the keyvault network settings.
Environment Summary
Additional context
No response