Status Update
No update yet.
Comments
rt...@google.com
Hello
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through
I recommend you to
I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you
de...@transect.com
pr...@google.com
Hello,
Thank you for your patience.
To investigate the issue properly the Product Team requires some information.
I have created a private issue to provide some information about the issue, for which you should have received an email notification. Please provide the requested information there and don't put any personal information, including project identifiers in this public issue.
di...@google.com
di...@google.com
Hello,
In order to troubleshoot this issue, we need some information like what URL are you hitting when you see the old version serve traffic?
de...@transect.com
For the details, I view the logs of each version to know which version is serving traffic.
And As per the details mentioned above, the older version with 0% traffic keeps on serving the newer request, the details of which can be verified through the logs for the older version.
Let me know if you need any more details related to this.
Thanks
di...@google.com
Hello,
What URL are you hitting when you see the old version continue to serve traffic?
de...@transect.com
de...@transect.com
di...@google.com
Hello,
Are you currently seeing this problem? Can you provide the version IDs of an old and new version that saw this behavior?
di...@google.com
hello,
We haven’t heard back from you for further troubleshooting the issue, I'm going to close this thread which will no longer be monitored. If the issue still persists please open a new Public Issue Tracker with a clear description of your issue and the steps to reproduce it by referencing this thread.
Description
We use the App Engine Flexible environment with custom runtime for executing long-running asynchronous tasks.
When we make changes to the app and deploy a new version using the command: "gcloud app deploy app.yaml", it deploys the new version routes 100% traffic to the newly deployed version, and stops the old version. This results in the failure of any requests that were in process on the old version.
To avoid the failing requests, we have tried keeping the old version alive by using the flag --no-stop-previous-version. In this case, even after the new version is deployed and the latest version is serving 100% of requests the new request keeps getting served by the older version.
Expected Behavior:
The version that shows serving 100% requests for the app engine in the GCP console should be processing any new incoming requests.
Steps to reproduce:
1. Deploy service on app engine flex environment.
2. Deploy an updated version without stopping the older version. using command: "gcloud app deploy --no-stop-previous-version app.yaml"
3. Wait for the new version to start successfully and start serving 100% traffic.
4. Make a request to the service running on the app engine.
5. The older version with 0% traffic set keeps on serving the new requests.
Other information (workarounds tried, documentation consulted, etc):
1. Tried command: gcloud app services set-traffic [MY_SERVICE] --splits [MY_VERSION]=1 for traffic migration
2. Tried command: gcloud app services set-traffic [MY_SERVICE] --splits [MY_VERSION1]=[VERSION1_WEIGHT],[MY_VERSION2]=[VERSION2_WEIGHT] --split-by [IP_OR_COOKIE]
3. Tried command: gcloud app services set-traffic s1 --splits=v2=.5,v1=.5
Tried traffic splitting, migration but all yield the same result, and the version showing 0% traffic in the GCP console keeps on serving the new requests until stopped.