-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
BUG: Create PrivateEndpoint using PrivateLink's alias may fail in concurrent creation scenario #20289
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @privlinksuppgithub. Issue DetailsWhen creating multiple PrivateEndpoints with PrivateLink's alias may fail with the following error message:
The put request to create the PrivateLink resource:
The request's body is: {
"location": "centralus",
"properties": {
"autoApproval": {
"subscriptions": [
"xxxxxxxxxxxxx"
]
},
"enableProxyProtocol": false,
"fqdns": [],
"ipConfigurations": [
{
"name": "primaryIpConfiguration-220818165005420368",
"properties": {
"primary": true,
"privateIPAddress": "",
"privateIPAddressVersion": "IPv4",
"privateIPAllocationMethod": "Dynamic",
"subnet": {
"id": "/subscriptions/xxxxxxxxxxxxx/resourceGroups/acctestRG-privatelink-220818165005420368/providers/Microsoft.Network/virtualNetworks/acctestvnet-220818165005420368/subnets/acctestsnetservice-220818165005420368"
}
}
}
],
"loadBalancerFrontendIpConfigurations": [
{
"id": "/subscriptions/xxxxxxxxxxxxx/resourceGroups/acctestRG-privatelink-220818165005420368/providers/Microsoft.Network/loadBalancers/acctestlb-220818165005420368/frontendIPConfigurations/acctestpip-220818165005420368"
}
],
"visibility": {
"subscriptions": [
"xxxxxxxxxxxxx"
]
}
},
"tags": {}
} The response is:
As we can see, the PrivateLink resource Then we sent a request to create a new PrivateEndpoint using this alias:
The body was: {
"location": "centralus",
"properties": {
"manualPrivateLinkServiceConnections": [
{
"name": "acctestPLS-220818165005420368",
"properties": {
"groupIds": [],
"privateLinkServiceId": "acctestpls-220818165005420368.b08a765d-0bcb-41bf-a0ec-755d43737dbc.centralus.azure.privatelinkservice",
"requestMessage": "test"
}
}
],
"privateLinkServiceConnections": [],
"subnet": {
"id": "/subscriptions/xxxxxxxxxxxxx/resourceGroups/acctestRG-privatelink-220818165005420368/providers/Microsoft.Network/virtualNetworks/acctestvnet-220818165005420368/subnets/acctestsnetendpoint-220818165005420368"
}
},
"tags": {}
} We used the PrivateLink's alias here, and the response was:
We believe this issue is caused by some cache-related issue on service side because:
We can reproduce this issue by creationg multiple PrivateLinks concurrently, then create a PrivateEndpoint with PrivateLink's alias. Can anyone help us solve this issue? Thanks!
|
…e issue Azure/azure-rest-api-specs#20289 no longer exist under API version 2023-09-01
…e issue Azure/azure-rest-api-specs#20289 no longer exist under API version 2023-09-01
When creating multiple PrivateEndpoints with PrivateLink's alias may fail with the following error message:
The put request to create the PrivateLink resource:
The request's body is:
The response is:
As we can see, the PrivateLink resource
acctestPLS-220818165005420368
was created successfully, it's alias wasacctestpls-220818165005420368.b08a765d-0bcb-41bf-a0ec-755d43737dbc.centralus.azure.privatelinkservice
Then we sent a request to create a new PrivateEndpoint using this alias:
The body was:
We used the PrivateLink's alias here, and the response was:
We believe this issue is caused by some cache-related issue on service side because:
We can reproduce this issue by creationg multiple PrivateLinks concurrently, then create a PrivateEndpoint with PrivateLink's alias. Can anyone help us solve this issue? Thanks!
The text was updated successfully, but these errors were encountered: