top | item 25962057

Google Cloud SQL Incident

54 points| keltex | 5 years ago |status.cloud.google.com | reply

11 comments

[+] zachberger|5 years ago|reply

> Instance creation, operations, and queries in us-central1 region may result in 502 (backend timeout) or 503 (service unavailable) errors.

[+] tzury|5 years ago|reply

https://status.cloud.google.com/incident/cloud-sql/21002

[+] nwsm|5 years ago|reply

Not seeing any issues in my side project's instance (us-central1-b).

[+] ashr|5 years ago|reply

Looks like something common between the control plane and data plane failed or there is a run-time dependency between the two (bad!) and that dependency failed.

[+] curiousDog|5 years ago|reply

how did you conclude that? Also, why is it bad to have common runtime dependencies between two services? Unless you mean a shared service.

[+] markyc|5 years ago|reply

also discussed here: https://news.ycombinator.com/item?id=25960649

[+] john37386|5 years ago|reply

Can it be link to CVE-2021-3156 ?

10 years old sudo vulnerability.

[+] Kwpolska|5 years ago|reply

No, it can’t. To exploit this vulnerability, you need the ability to run shell commands/arbitrary code on the system. Google Cloud SQL only lets you run SQL, and I would expect the servers to be locked down pretty heavily when it comes to non-database stuff.