-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Creation of private Endpoint for Container Registry fails with "Private Endpoint needs to be reconfigured with missing memberNames." #21781
Comments
@sunilr8 Thank you for submitting this! From the error message, you probably need to explicitly set the |
@magodo, thanks looking into this. I am seeing same issue with registry_data_eastus2 also : creating Private Endpoint "pep-conreg-dev" (Resource Group "rg-test-infra-dev-eu2"): network.PrivateEndpointsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="PrivateEndpointIpConfigurationMissingMemberNamesRequiredByFps" Message="Private Endpoint /subscriptions/*****/resourceGroups/rg-test-infra-dev-eu2/providers/Microsoft.Network/privateEndpoints/pep-conreg-dev contains static ipconfigurations: [PrivateIPAddress: 172.21.35.8, GroupId: registry, MemberName: registry_data_eastus2] and its missing these membernames/groupids requested by Private Link service [GroupId: registry, MemberName: registry]. Private Endpoint needs to be reconfigured with missing memberNames." Details=[] |
@sunilr8 Per this document: https://learn.microsoft.com/en-us/azure/private-link/manage-private-endpoint?tabs=manage-private-link-cli#determine-groupid-and-membername, what is the output by running the Meanwhile, are you able to create the PE with the static assigned ip via other means? In which case, would you mind to paste the response of the successfully created PE? |
I'm facing a similar issue: ip_configuration { Error: Error: creating Private Endpoint "xxxxxx" (Resource Group "xxxx"): network.PrivateEndpointsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="PrivateEndpointIpConfigurationMissingMemberNamesRequiredByFps" Message="Private Endpoint /subscriptions/xxxxxx/resourceGroups/xxxxx/providers/Microsoft.Network/privateEndpoints/xxxxxxx contains static ipconfigurations: [PrivateIPAddress: xxx.xx.xx.xx, GroupId: registry, MemberName: default] and its missing these membernames/groupids requested by Private Link service [GroupId: registry, MemberName: registry_data_westeurope; GroupId: registry, MemberName: registry]. Private Endpoint needs to be reconfigured with missing memberNames." Details=[] @magodo, could you please help? |
Creating the PE for a container registry, there needs two
|
How do you locate the member_name? I can find a subresource name from Microsoft, but it seems like the member_name is only available if you dynamically create the PE first. |
Is there an existing issue for this?
Community Note
Terraform Version
1.4.6
AzureRM Provider Version
3.50.0
Affected Resource(s)/Data Source(s)
azurerm_container_registry private_endpoint_account
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
private endpoint with static ip should be created
Actual Behaviour
creating Private Endpoint "pep-conreg-dev" (Resource Group "rg-test-infra-dev-eu2"): network.PrivateEndpointsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="PrivateEndpointIpConfigurationMissingMemberNamesRequiredByFps" Message="Private Endpoint /subscriptions/******/resourceGroups/rg-test-infra-dev-eu2/providers/Microsoft.Network/privateEndpoints/pep-conreg-dev contains static ipconfigurations: [PrivateIPAddress: 172.21.35.8, GroupId: registry, MemberName: registry] and its missing these membernames/groupids requested by Private Link service [GroupId: registry, MemberName: registry_data_eastus2]. Private Endpoint needs to be reconfigured with missing memberNames." Details=[]
Steps to Reproduce
please update sample code above with as per your enviroment (network rg ,subnet, zoneid and etc)
terraform init
terraform apply
Important Factoids
na
References
(#19094)
The text was updated successfully, but these errors were encountered: