Unfortunately, after much effort and many attempts, I have not been able to reproduce this issue. Immediately after deployment, even in some cases before *appcfg.py* and *gcloud app deploy* confirm that deployment was successful, requests are appropriately routed to *module B* as expected.
Should you continue to face this issue and can provide logs for deployment times, dispatch yaml and requests incorrectly routed, please file a defect report on the App Engine public issue tracker <https://code.google.com/p/googleappengine/issues/list> so that we may attempt to investigate this further while this is in effect. On Monday, July 4, 2016 at 1:54:13 PM UTC-4, Mayank Bhagya wrote: > > We have a jenkins push-to-deploy setup that uses gcloud to deploy an > appengine application. > > After the deployment, suddenly all requests going to a module B start > going to a module A (default module)!? > > How is that possible? > Why is the dispatcher screwed up after a 'gcloud preview app deploy'. > This has hurt many of our users today. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/71cc662f-251b-42bc-ad73-c07e30779306%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
