Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AllowMultipleAddressPrefixesOnSubnet not available #18194

Open
arjun-virmani opened this issue May 24, 2021 · 6 comments
Open

AllowMultipleAddressPrefixesOnSubnet not available #18194

arjun-virmani opened this issue May 24, 2021 · 6 comments
Assignees
Labels
feature-request Network az network vnet/lb/nic/dns/etc... p2_e2 priority=2 emergency=2
Milestone

Comments

@arjun-virmani
Copy link

[Enter feedback here]

Multiple address prefixes feature not allowed as of now, so it should be removed, terraform reference to this should also be edited. It is not even in preview. AllowMultipleAddressPrefixesOnSubnet feature needs to be registered for this, which isn't allowed as of now.

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@ghost 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 May 24, 2021
@yonzhan yonzhan added the Network az network vnet/lb/nic/dns/etc... label May 24, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label May 24, 2021
@yonzhan yonzhan removed the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label May 24, 2021
@yonzhan yonzhan added this to the S188 milestone May 24, 2021
@yonzhan
Copy link
Collaborator

yonzhan commented May 24, 2021

network

@kairu-ms kairu-ms added the p2_e2 priority=2 emergency=2 label May 27, 2021
@yonzhan yonzhan modified the milestones: S188, S189 Jun 13, 2021
@yonzhan yonzhan modified the milestones: S189, Jul 2021 (2021-08-03) Jul 2, 2021
@JLunda
Copy link

JLunda commented Jul 14, 2021

I am experiencing this issue with this feature and have attempted this:

az feature register --namespace Microsoft.Network -n AllowMultipleAddressPrefixesOnSubnet --subscription <subscriptionId>

Using az feature show --namespace Microsoft.Network -n AllowMultipleAddressPrefixesOnSubnet --subscription <subscriptionId>, I can see the registration is in status Pending, but I am interested in why the original reporter of this issue says the feature is not allowed and in an estimated timeframe by which this feature is expected to reach Registered status.

Thank you!

@arjun-virmani-by
Copy link

I am experiencing this issue with this feature and have attempted this:

az feature register --namespace Microsoft.Network -n AllowMultipleAddressPrefixesOnSubnet --subscription <subscriptionId>

Using az feature show --namespace Microsoft.Network -n AllowMultipleAddressPrefixesOnSubnet --subscription <subscriptionId>, I can see the registration is in status Pending, but I am interested in why the original reporter of this issue says the feature is not allowed and in an estimated timeframe by which this feature is expected to reach Registered status.

Thank you!

Hi Jordan,

I spent some couple of days on the same issue. Seems like Terraform has this in documentation on the basis of azure documentation, which is incorrect in the first place.

After going back and forth with Azure support that this feature isn't even in preview by then(not sure of now), they mistakenly showed it in the documentation and features. Its for internal engineers use, as per them. Enclosing the screenshot.
Screenshot 2021-07-15 at 1 29 23 PM
Thanks.

@JLunda
Copy link

JLunda commented Jul 15, 2021

Thanks for the additional information, @arjun-virmani-by. I can confirm that I have tried via AZ CLI and ARM template and this feature fails both ways. I also spent some time talking to Azure Support and was likewise informed that this feature is not ready for General Availability (GA). I would second the need for the documentation to have a note that conveys this information or to be modified not to mention the ability to pass multiple address prefixes, since it is not ready yet. Thanks!

@Lau-rawr
Copy link

any update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Network az network vnet/lb/nic/dns/etc... p2_e2 priority=2 emergency=2
Projects
None yet
Development

No branches or pull requests

9 participants