Database Migration Service broken for us-central1? Stuck on spinner on "Create New Migration"

[pfath]

I was testing the Database Migration Service. Last week, I was able to create a Database Migration job and migrate Postgres data from one Cloud SQL database to a new one (wanted to reduce storage costs).

However, this week (starting 12/23, but continuing today, 12/24), I can't get past the "Get started" screen on "Create a migration job." I fill in the details and then click "Save and Continue," and I just get these never-ending spinners. I tried with Postgres and with MySQL. I tried with eu-west1 and asia-east1 and it seemed to continue, so I think maybe something is broken in us-central1? But my DB is in us-central so I don't think I can just set up the migration job elsewhere. Is anyone else running into this? I also tried other projects with the same failed result...

[KyleMari]

Hi @pfath,

Currently, there are no known incidents or reports similar to this issue. I also tried to reproduce this by creating a sample migration job on my end while able to supply a source database and a host IP address. I made sure to set the region to "us-central1". Based on my result however, I was able to get past the "Get Started" screen.

Could you confirm if you're still experiencing the infinite loading spinner while creating a job? If so, try to clear cache, restart browser, or use incognito mode. If you're using Chrome, you can check the Developer Tools Console for any possible errors raised by the Google Cloud console page.

In addition, you can also use REST API as a workaround when creating a new Database Migration Job to carry out your migration plan.

If the issue persists, I'd recommend reaching out to Google Cloud support for urgent help to get this issue investigated. Alternatively, you can share your observations by filing a public issue tracker here, which will be looked at by the Database Migration Service team. Note though that I won't be able to confirm the exact turn around time for issue resolution when it comes to submitted public issue tracker tickets.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[pfath]

OK after tinkering some more, trying different browsers, incognito, and the REST API, I figured out what I think is a bug with the UI. I finally found that my migration jobs were being created and going into the "Drafts" tab. So it seems that the infinite spinner is just a UI bug; the backend was actually creating the draft job, but the UI wasn't updating to show success. I was able to walk through a bunch of migration steps and eventually get some data migrated, but it was a lot of clicking out and in to figure out when things completed (there were other places with infinite spinners too). 

I think this will suffice for me to do this one-time migration, but it's frustrating to deal with the spinners and clicking around to find out when things are finished.

[clouduser809989]

I'm experiencing the same issue now, in europe-west3 (Frankfurt). Also I've tried few other EU regions, and the result is the same. Every step stucks when I press "Save and continue". Then I go to "Migration jobs > Drafts", open my job, and it takes me to the next step. But in my case I had one more issue: I was trying to setup Amazon RDS MySQL 5.7 to Cloud SQL migration, and I was trying to choose existing Cloud SQL MySQL 5.7 instance as a destination. But in this case it was not letting me go further than fourth step (Define connectivity method). The issue was the same, when pressing "Save and continue", it's spinning forever. The solution in my case was to create new instance during third step (Define a destination) instead of using existing one. And I don't say this solution solved everything, I still had to open migration job after each step in drafts, but at least I've managed to create the job, and later run it.

I've done all I wanted, and leaving this message for those who will have the same issues as me.