You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
az feedback auto-generates most of the information requested below, as of CLI version 2.0.62
Describe the bug
The IPv6 subnet can be successfully created using the CLI, but it cannot be viewed and referenced by azure portal
To Reproduce
Can Work Code:
az network vnet subnet create
--address-prefixes '10.1.2.0/24' 'ace:cab:decb:deed::/64'
--name TestIPv6Subnet
--resource-group sam-test-resource-group
--vnet-name samtestresourcegroupvnet150
Can't work code:
az network vnet subnet create
--address-prefixes 'ace:cab:decb:deed::/64' '10.1.2.0/24'
--name TestIPv6Subnet
--resource-group sam-test-resource-group
--vnet-name samtestresourcegroupvnet150
The text was updated successfully, but these errors were encountered:
ghost
added
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
labels
Sep 20, 2020
yonzhan
added
Network
az network vnet/lb/nic/dns/etc...
and removed
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
labels
Sep 20, 2020
Describe the bug
The IPv6 subnet can be successfully created using the CLI, but it cannot be viewed and referenced by azure portal
To Reproduce
Can Work Code:
az network vnet subnet create
--address-prefixes '10.1.2.0/24' 'ace:cab:decb:deed::/64'
--name TestIPv6Subnet
--resource-group sam-test-resource-group
--vnet-name samtestresourcegroupvnet150
Can't work code:
az network vnet subnet create
--address-prefixes 'ace:cab:decb:deed::/64' '10.1.2.0/24'
--name TestIPv6Subnet
--resource-group sam-test-resource-group
--vnet-name samtestresourcegroupvnet150
The text was updated successfully, but these errors were encountered: