Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
customer message: at 9:04pm PT today Google Front End (GFE) started returning 500 to clients even though our app server logs returned 200.
This is creating critical service degradation because the clients think the requests failed when they in fact succeded.
We've confirmed in our app logs and documented here: ( Attached)
There is no incident on the GCP status page, and we have made no changes to our application.
What you expected to happen:
Steps to reproduce:
GCP project id: camiologger
GCP project number: 95613839261
GCP camiologger application
The doc also include log lines showing the problem and a quick observation that approximately 1 in 6 requests seem to return the correct 200 (with the others getting 500 from GFE even though our app returned 200).
Other information (workarounds you have tried, documentation consulted, etc):