Traffic migrate between versions is stuck

[Joachim Stokke]

Hi guys! I've got myself in a bind here. 

I accidentally deployed a java 8 compiled version to app engine, and then hit the migrate traffic button.. The traffic migration is now stuck, because the new version is not working (or at least that's what I presume is why it's stuck). I also cannot update the java 8 version to fix it because it's blocked by the traffic migration process.

I wrote a StackOverflow question here: http://stackoverflow.com/questions/32611549/is-there-a-way-to-cancel-traffic-migration-in-google-app-engine

I was also able to reproduce this in a fresh project, but right now I just need help to get unstuck from this. 

I hope someone from support can take a look at this for me! (or if anyone has any suggestions on how to fix it).

Thank you!

[Nick (Cloud Platform Support)]

Hey Joachim,

This definitely seems like something that shouldn't occur. If the new version has fatal errors, the infrastructure managing the migration should detect this and back off, eventually terminating the migration status. Feel free to open a public issue tracker issue as type-production detailing the problem and you'll hopefully get some help shortly. You can rely on guaranteed response times with a support package, but you can always use the public issue tracker to report an issue.

Best wishes,

Nick 

[Joachim Stokke]

Hi Nick!

I agree this should not happen. I was able to reproduce it as well on a new project. Upload a second version that is corrupt, then try migrate traffic. It gets stuck. 

However thanks to your suggestion on stackoverflow about doing a rollback, it has been un-stuck :) 

Thank you so much!

[Nick (Cloud Platform Support)]

Hey Joachim,

It's great to hear you managed to fix it with rollback. That can usually be used when a deployment is stuck.

Best wishes,

Nick