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.

Sign up for GitHub

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

Jump to bottom

PostgreSQL create virtual network rule returns 202 although IgnoreMissingVnetServiceEndpoint is set to false #3719

Closed
vladbarosan opened this issue Aug 24, 2018 · 7 comments
Closed

PostgreSQL create virtual network rule returns 202 although IgnoreMissingVnetServiceEndpoint is set to false #3719

vladbarosan opened this issue Aug 24, 2018 · 7 comments
Assignees
@sergey-shandar
Labels
PostgreSQL Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@vladbarosan
Copy link

vladbarosan commented Aug 24, 2018 •
edited
Loading

For details Azure/azure-sdk-for-go#2534
@vladbarosan
Copy link
Author

Taking the history of PosgreSQL, @QingqingYuan can you help the customer here ?

@WodansSon
Copy link
Contributor

Adding link to Provider PR

@bsiegel bsiegel added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 26, 2018
@QingqingYuan2
Copy link
Contributor

Provider PR is designed this as async operation. The operation result will return "Bad Request" in this case.

@aullom1
Copy link

aullom1 commented Nov 30, 2018

The bug as it is reported, and the PR, deal entirely with PostgreSQL. However, this is also a problem with MySql. Do you want a new bug for this, or is it appropriate to fix IgnoreMissingVnetServiceEndpoint for all databases?

@QingqingYuan2
Copy link
Contributor

We handle both of the databases together. No need for separate bug.
This bug has been fixed from RP side. PostgreSQL and MySQL both return 400 when "IgnoreMissingVnetServiceEndpoint" is set to false while vnet is not enabled the service.

@hovsepm hovsepm removed their assignment Jan 23, 2019
@rachel-msft
Copy link

This was fixed in November as Qingqing mentioned. Please close @hovsepm.

@rachel-msft
Copy link

@aullom1, @hovsepm, @jeffreyCline could you help with closing this issue?

@djsly djsly mentioned this issue Oct 11, 2019
Closed
@anttisiiskonen anttisiiskonen mentioned this issue Aug 11, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sergey-shandar sergey-shandar

Labels
PostgreSQL Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@bsiegel @sergey-shandar @azuresdkci @hovsepm @vladbarosan @WodansSon @aullom1 @aamalvea @rachel-msft @QingqingYuan2