Assigned
Status Update
No update yet.
Comments
co...@closte.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
ba...@google.com
ba...@google.com
One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.
Description
I will try to explain the problem and the use case as much as I can.
Recently, Google Cloud had a major downtime in the complete eu-west-9 (Paris) region, so in the first few days, we couldn't use any feature in this region.
Issue:https://status.cloud.google.com/incidents/dS9ps52MUnxQfyDGPfkY
After a few days, once two zones and a few services were restored, we didn't have SnapShots anymore because your system is deleting the already created SnapShots, even though the server status is "Repairing" and all new "Create new SnapShot" tasks are not working.
So, just after a few days, we are in the following situation:
So, the only option was to wait 10+ more days for the restoration of the eu-west-a zone. After so many days, the eu-west-a zone was restored but the server wasn't booting because the disk was corrupted, so we were in a situation like:
As you can see, we are in a situation to lose everything, even we have Snapshots and the server was working fine.
A similar scenario can happen even if the region is 100% working because you are deleting the Snapshots without ensuring the new Snapshot can be successfully created.
This does not make any sense, it's an IQ bug. Here is how it should work:
You must have a new option, something like "Keep minimum XX number of the latest snapshots" (ui.jpg image).
Real-life scenario:
With this setup and options, even if the region is completely offline for 4 months or you are not able to create new Snapshots for 6 months, I will still have snapshots, at least the latest 2 successful snapshots!!!