Incident affecting Cloud Memorystore
Cloud Redis BASIC Tier Instances cannot proceed version upgrade after their maintenance or capacity update
Incident began at 2022-06-24 03:37 and ended at 2022-06-29 01:56 (all times are US/Pacific).
Previously affected location(s)
Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Melbourne (australia-southeast2)Warsaw (europe-central2)Finland (europe-north1)Madrid (europe-southwest1)Belgium (europe-west1)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Paris (europe-west9)Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Santiago (southamerica-west1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Columbus (us-east5)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)
| ||29 Jun 2022||01:56 PDT|| |
We experienced an intermittent issue with Cloud Memorystore beginning at Wednesday, 2022-06-22 21:42 US/Pacific.
The issue has been resolved for all affected projects as of Wednesday, 2022-06-29 01:50 US/Pacific.
We thank you for your patience while we worked on resolving the issue.
| ||24 Jun 2022||04:12 PDT|| |
Summary: Cloud Redis BASIC Tier Instances cannot proceed version upgrade after their maintenance or capacity update
Description: Mitigation work is still underway by our engineering team.
The mitigation is expected to complete by Friday, 2022-07-01 06:00 US/Pacific.
We will provide more information by Wednesday, 2022-06-29 06:00 US/Pacific.
We apologize to all who are affected by the disruption.
Diagnosis: Once the Basic Tier Instance went through a maintenance or a capacity update, it will fail all the version upgrade requests due to internal error (with code 13). Version upgrade behavior can be found under: https://cloud.google.com/memorystore/docs/redis/version-upgrade-behavior
Workaround: None at this time