Cannot create a Postgres Cloud SQL instance on Milan (europe-west8) region

[gionn]

Hello,

I was trying to evaluate running a Postgres 14 instance on the europe-west8 region but even if retrying with different type of configurations and also on the command line, I always get a general failure without no further hints:

gcloud sql instances create my-test-dev-mi \
--cpu=1 \
--memory=3840MB \
--database-version=POSTGRES_14 \
--region=europe-west8


Creating Cloud SQL instance for POSTGRES_14...failed.
ERROR: (gcloud.sql.instances.create) [INTERNAL]

[ms4446]

The error message you're seeing, [INTERNAL], typically indicates an internal error with Google Cloud. However,  the Google Cloud Status Dashboard does not show any issues for the 'europe-west8' (Milan) region and the Google Cloud SQL service is listed as available.

https://status.cloud.google.com/regional/europe

Here are  some general troubleshooting steps you can try:

• Try creating an instance in another region to see if the issue is specific to 'europe-west8'.
• Verify your project's quota in the Google Cloud Console to ensure you have enough resources available for the instance you're trying to create.
• Check if there are any network restrictions that might be preventing the connection to Google Cloud SQL.

If none of these steps resolve the issue, I recommend contacting Google Cloud Support for further assistance.

[gionn]

---

@ms4446 wrote:

Try creating an instance in another region to see if the issue is specific to 'europe-west8'.

---

Forgot to mention that, but yes, I tried creating a bunch of sql instances in different EU regions and only Milan seems the one affected.

---

@ms4446 wrote:

• Verify your project's quota in the Google Cloud Console to ensure you have enough resources available for the instance you're trying to create.
• Check if there are any network restrictions that might be preventing the connection to Google Cloud SQL.

---

Don't think is any configuration issue on my side because it's a new project that I've created just for this purpose and nothing else, quotas are all fine.

---

@ms4446 wrote:

I recommend contacting Google Cloud Support for further assistance.

---

Unfortunately I don't have paid access to support and I hoped writing here would have been a place to at least rise the issue.

Thanks for your reply!

[wahid]

I am getting the exact same error while trying to clone an existing Postgres 9.6 instance. It's happening for a specific zone (europe-north1-b) but the same cloning option is working in europe-north1-a for another project with postgres 10. 

[ms4446]

Here are a few things you could try:

1. Check the instance configurations: Make sure that the configurations of the instance you're trying to clone are compatible with Postgres 14. Some settings or features in Postgres 9.6 might not be available or might work differently in Postgres 14.

2. Try creating a new instance without cloning: If possible, try creating a new Postgres 14 instance without cloning from the existing Postgres 9.6 instance. If this works, you can then import the data from the 9.6 instance to the 14 instance.

[wahid]

Thank you for your suggestions. However, I don't think that's what I want to do actually. I am pretty new to my current workplace and still don't know all the application side code that might be affected if I create a new instance with new connection details. I don't really know how many things it will break and for production environments, this is not just an option. I am facing the problem in testing environment, staging worked where I could clone the database instance. Haven't touched the production environments yet.

[ms4446]

I understand your concerns. Here are a few more suggestions:

1. Try cloning in a different zone: If possible, try cloning the instance in a different zone. This might help you determine whether the issue is specific to the europe-north1-b zone.

2. Check the logs: Google Cloud SQL provides logs that can help you diagnose issues. Check the logs for the instance you're trying to clone to see if there are any error messages or warnings that might give you more information about the issue.

3. Check the instance's resource usage: If the instance you're trying to clone is using a lot of resources (CPU, memory, disk space, etc.), it might be causing issues with the cloning process. You can check the instance's resource usage in the Google Cloud Console.

[wahid]

Thank you for your response and ideas. Unfortunately, the cloning options from console currently I see is cloning the current configuration only. There is no option to change the version or zone/region. As I mentioned, I have postgres 10, if the cloning is successful, it will be postgres 10 for the cloned instance. There is no way /and rightly so) to clone the database as postgres 14 from 10. That's not what I am trying as well. I want to upgrade the cloned instance after the cloning is successful before I touch my main instance to start upgrading.

[ms4446]

Unfortunately, it's not possible to clone a PostgreSQL instance and specify a different version. The cloned instance will always be the same version as the original instance.

However, you can upgrade a PostgreSQL instance to a newer version without having to clone it first. To do this, you can use the gcloud sql instances upgrade command. For example, the following command would upgrade a PostgreSQL instance named my-instance to version 14:

gcloud sql instances upgrade my-instance --database-version=POSTGRES_14

This command will upgrade the instance in place, so you won't need to create a new instance or transfer any data.