Re: cloud sql failover instance connecting to wrong master instance

[Carlos (Cloud Platform Support)]

I was not able to reporduce your scenario. These are the steps I followed. 

1- Created a Cloud SQL  second generation instance named "master-instance-a" and setup root password

2- Cloned the instance to "master-instance-b"

3- Added the failover to the cloned instance using the console.  The server deployed with no errors.

Since in this first test the original instance did not had a failover, I tested again

4- I cloned Master-Instance-b (which now had a failover) and created "master-instance-c"

5- Add a failover. 

After that I had the following servers:

~$ gcloud sql instances list

NAME                         DATABASE_VERSION  REGION       TIER              ADDRESS         STATUS

master-instance--c           MYSQL_5_7         us-central1  db-n1-standard-1  xxxxxxxxxxxxxx  RUNNABLE

master-instance--c-failover  MYSQL_5_7         us-central1  db-n1-standard-1  xxxxxxxxxxxxxx  RUNNABLE

master-instance-a            MYSQL_5_7         us-central1  db-n1-standard-1  xxxxxxxxxxxxxx  RUNNABLE

master-instance-b            MYSQL_5_7         us-central1  db-n1-standard-1  xxxxxxxxxxxxxx  RUNNABLE

master-instance-b-failover   MYSQL_5_7         us-central1  db-n1-standard-1  xxxxxxxxxxxxxx  RUNNABLE

How dows it look for your project when you list the instances using the CLI? You can try to delete any undesired instances via the CLI. Can you provide details on the command used to connect to the failover?

[Carlos (Cloud Platform Support)]

Please open a report in the issue tracker since we will need to work on your particular project.