Service Health
Incident affecting Google Kubernetes Engine, Google Cloud Composer, Google Cloud Dataproc
Google Kubernetes Engine Autopilot cluster creation, Google Cloud Dataproc serverless job submission and Google Cloud Composer environment creation are experiencing elevated error rates.
Incident began at 2023-02-07 11:50 and ended at 2023-02-07 19:53 (all times are US/Pacific).
Previously affected location(s)
London (europe-west2)Frankfurt (europe-west3)Iowa (us-central1)South Carolina (us-east1)
Date | Time | Description | |
---|---|---|---|
| 7 Feb 2023 | 19:53 PST | The issue with Google Cloud Composer, Google Cloud Dataproc, Google Kubernetes Engine has been resolved for all affected users as of Tuesday, 2023-02-07 19:45 PST US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 7 Feb 2023 | 17:55 PST | Summary: Google Kubernetes Engine Autopilot cluster creation, Google Cloud Dataproc serverless job submission and Google Cloud Composer environment creation are experiencing elevated error rates. Description: Mitigation work is currently underway by our engineering team and is on track to be completed by Tuesday, 2023-02-07 20:15 US/Pacific. We will provide more information by Tuesday, 2023-02-07 20:20 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: Customers can use unaffected regions where feasible. |
| 7 Feb 2023 | 17:30 PST | Summary: Google Kubernetes Engine Autopilot cluster creation, Google Cloud Dataproc serverless job submission and Google Cloud Composer environment creation 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 18: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: Customers can use unaffected regions where feasible. |
| 7 Feb 2023 | 16:35 PST | 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:40 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. |
| 7 Feb 2023 | 16:26 PST | 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. |
- All times are US/Pacific