Google Kubernetes Engine Autopilot cluster creation, Google Cloud Dataproc serverless job submission and Google Cloud Composer environment creation are experiencing elevated error rates.
ResolvedMinor
February 07, 2023 - Started almost 3 years ago
- Lasted about 4 hours
Incident Report
Summary: Google Kubernetes Engine, Google Cloud Dataproc and Google Cloud Composer are experiencing elevated error rates.
Description: Mitigation work is currently underway by our engineering team.
The mitigation is expected to complete by Tuesday, 2023-02-07 20:15 US/Pacific.
We will provide more information by Tuesday, 2023-02-07 17:30 US/Pacific.
Diagnosis:
**Google Kubernetes Engine :**
Customer attempting to create Autopilot clusters may receive error message like message: "Invalid usage of the resource: Invalid resource usage: 'Invalid resource name (using reserved prefix):" resulting in Autopilot cluster creation failures.
**Google Cloud Dataproc:**
Customers attempting to submit serverless jobs in the affected regions will encounter error message "Invalid resource usage: 'Invalid resource name (using reserved prefix): "
**Google Cloud Composer:**
Cloud Composer creations in the affected regions are failing with error message "CREATE operation failed. Polled operation status: DONE: Google Compute Engine: Invalid resource name (using reserved prefix): "
Workaround: None at this time.
Need to monitor Google Cloud outages?
Monitor all your external dependencies in one place
Get instant alerts when outages are detected
Be the first to know if service is down
Show real-time status on private or public status page
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.