Assigned
Status Update
Comments
va...@google.com <va...@google.com>
ku...@google.com <ku...@google.com> #3
Hi, this error only affects Cloud SDK version 186. It was previously reported in Issue 72407295 and a fix for it should be released in Cloud SDK version 187.
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
to...@gmail.com <to...@gmail.com> #4
It's been a while - any update on this?
to...@gmail.com <to...@gmail.com> #5
Hello?!
Description
Problem you have encountered:
During subsequent deployment of a standard environment, manually scaled PHP service to App Engine, when an old instance is being terminated the request to
/_ah/stop
results in a 500 response.What you expected to happen:
The requests to
/_ah/stop
should result in a 200 responseSteps to reproduce:
gcloud app deploy app.default.yaml --ignore-file=.gcloudignore
gcloud app deploy app.default.yaml --ignore-file=.gcloudignore
Other information (workarounds you have tried, documentation consulted, etc):
A minimal demo project can be found here . The
README
explains the problem in detail.Using
gcloud app deploy
results in the/_ah/stop
request propagating to the deployed PHP code when it shouldn't. Manually deleting an instance using the GCP console correctly intercepts the request to/_ah/stop
before it reaches the deployed PHP code.