Closed v-ruizh closed 7 months ago
Verified this bug on a newer build 20230927.1, the error message changes. You can get the details from below. The below error shows when creating a new database for Single PostgreSQL server. The below error shows when creating a new database for Flexible PostgreSQL server.
I believe this has been fixed.
Verified this bug on the latest build 20231017.2, this issue also reproduces. You can get the details from below. The below error shows when creating a new database for Single PostgreSQL server. The below error shows when creating a new database for Flexible PostgreSQL server.
I believe this has been fixed.
I am still getting this. My copy of MS Code is up to date. Azure extension installed a day or two ago.
I am still not able to reproduce this problem. The "ECONNRESET" error hints that it might have something to do with a transient network issue. If you can ever reproduce this issue, could you go to the Output panel in VSCode and get the output from the extension like my screenshot shows? It would help further investigate the issue if I can know which stage failed.
@JasonYeMSFT Verified this issue on the current released Azure Databases extension v0.20.0, this issue also reproduces. The repro steps and output show as below.
Can't verify this issue on the latest main branch build 20240109.2 due to the known bug https://github.com/microsoft/vscode-cosmosdb/issues/2209.
OK. It seems like the datebase creation was successful but the follow up access didn't work. Could you go to Azure Portal, navigate to the postgres database resource > Networking blade and see if the current IP detected by Azure Portal matches the IP address printed in the output? The IP detection logic we use may not guarantee that the IP address we add to the firewall rule is the actual IP address used to connect to the database.
Checked the current IP in Azure Portal, the current IP detected by Azure Portal matches the IP address printed in the output.
OK, however, unfortunately there is no way for us nor Portal to guarantee the IP address we detect will be used to connect. For everyone who encounters the ECONNRESET error, please consult your local network admin to see if they can help you figure out at which stage does the network reset happens.
I found a bug while looking into #2224. I am going to close this issue since it is more related to the firewall setting.
OS: Win10 Build Version: 20230919.6
Repro Steps:
Expect: Succeed to create a database for PostgreSQL server without any error.
Actual: Fail to create a database for PostgreSQL server with an error.
More Info: This issue reproduces for both single and flexible PostgreSQL server.