Gke AI Troubleshooting Tpu Slice Mig Stuck Updating
GoogleOfficialPublished by Google
- Skill
- Review and audit
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a diagnostic workflow to troubleshoot GKE TPU Dynamic Slice creation failures and JobSet scheduling delays. It specifically targets scenarios where the underlying Compute Engine Managed Instance Groups (MIGs) are in an unstable state (isStable=False), preventing successful slice formation. The skill guides the user through identifying the affected MIG, checking its stability status, investigating ongoing node pool operations like upgrades or repairs, and applying appropriate resolutions.
What it does
- Identifies the specific MIG backing a failing TPU node pool.
- Checks MIG stability status and version target completion.
- Queries Cloud Logging for errors related to the instance group manager.
- Detects if node pool upgrades or automated repairs are blocking slice creation.
- Provides resolution steps for capacity issues, quota errors, or stuck node pool operations.
- Verifies recovery of the Slice custom resource after MIG stabilization.
When to use it
- When TPU slice creation fails with a SliceCreationFailed status reason.
- When JobSets remain stuck in a pending state.
- When MIG status indicates isStable=False or versionTarget.isReached=False.
- When you suspect underlying infrastructure instability is blocking TPU resource allocation.
Advantages
- Systematic approach to isolating infrastructure-level blockers for TPU slices.
- Prevents manual interference by providing safe, read-only diagnostic steps.
- Clearly distinguishes between infrastructure instability and workload configuration issues.
- Provides actionable guidance for common GKE node pool and MIG lifecycle operations.
Usage examples
- “My TPU slice creation is failing with SliceCreationFailed. How do I check if the backing MIG is the cause?”
- The agent will guide you through collecting the MIG name, checking its isStable status, and reviewing logs for errors to confirm if the MIG is currently updating or unstable.
- “My JobSet is stuck in pending and the TPU slice isn't becoming active. What should I look for?”
- The agent will help you inspect the Slice custom resource conditions and verify if the underlying node pool is undergoing an upgrade or repair that is preventing the slice from reaching an ACTIVE state.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/gke-ai-troubleshooting-tpu-slice-mig-stuck-updating/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip gke-ai-troubleshooting-tpu-slice-mig-stuck-updating.zip -d .agents/skills
Documentation by Google
Troubleshoot GKE TPU slice creation blocked by an unstable MIG
This skill helps diagnose GKE TPU Dynamic Slice creation failures and JobSet
scheduling delays when the Compute Engine managed instance groups (MIGs) that
back the TPU node pool aren't stable (status.isStable: false).
A SliceCreationFailed status reason means that slice creation failed because
prerequisites weren't met (for example, required Compute Engine resources are
missing) or preflight checks failed (see
Use dynamic slicing with a custom scheduler).
A MIG that is still creating, updating, or repairing instances is one cause to
check. This skill checks the slice status first, then the stability of the
backing MIGs.
Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read Usage Attribution. For commands executed
directly in the terminal (never in generated scripts, Terraform, or user code),
prefix gcloud with
CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:gke-ai-troubleshooting-tpu-slice-mig-stuck-updating)"
and append agent-skills/1.0 (skill:gke-ai-troubleshooting-tpu-slice-mig-stuck-updating) to User-Agent headers.
Prerequisites
Google Cloud SDK & Tools:
For installing and initializing
gcloud(project selection and authentication) and enabling the GKE API, follow Before you begin.For installing
kubectland configuring cluster credentials, follow the "Install kubectl", "Install required plugins", and "Store cluster information for kubectl" sections of Install kubectl and configure cluster access.
API Enablement & Billing:
Verify that the project has an active Cloud Billing account.
Enable APIs:
container.googleapis.com,compute.googleapis.com, andlogging.googleapis.com.
Required IAM Roles:
Logs Viewer (
roles/logging.viewer): Inspect Cloud Audit Logs for MIG errors.Compute Viewer (
roles/compute.viewer): Check MIG stability (isStable) and instance progress.Kubernetes Engine Viewer (
roles/container.viewer): Inspect Slice custom resources (slices.accelerator.gke.io), nodes, and cluster operations.
Documentation:
Use dynamic slicing with a custom scheduler (Sections: "Before you begin", "Create a Slice custom resource", "Monitor the status of the Slice custom resource", "Verify the status of the nodes and the partitions", "Upgrade your node pools")
Install kubectl and configure cluster access (Sections: "Install kubectl", "Install required plugins", "Store cluster information for kubectl")
Add and manage node pools (Sections: "View node pools in a Standard cluster")
View information about MIGs and managed instances (Sections: "Check whether a MIG is stable", "Check the status of managed instances", "List instance errors")
Automatically apply VM configuration updates in a MIG (Sections: "Verify whether an update rollout is complete")
Manually upgrade a cluster's control plane or node pools (Sections: "Check node pool upgrade status", "Cancel a node pool upgrade", "Resume a node pool upgrade", "Roll back a node pool upgrade")
Auto-repair nodes (Sections: "Get information about recent automated repair events")
Troubleshoot GKE Standard node pools (Sections: "Issue: Node pool creation fails due to insufficient resources")
Troubleshoot TPUs in GKE (Sections: "Insufficient quota to satisfy the TPU request", "Insufficient TPU resources to satisfy the TPU request")
REST Resource: projects.locations.clusters.nodePools (Sections: "Resource: NodePool")
Schedule dynamic slices with Kueue and TAS (Sections: "Monitor the status of the slice")
Get support (Sections: "Before you contact support")
Read-only rule: Run read-only diagnostic commands only. Never drain, delete, or re-create nodes, or run any other command that changes the cluster. Give the user any fix to apply themselves.
When you recommend a fix, link the doc section that describes it.
Diagnostic workflow
Step 0: Collect context and set the investigation window [Low Risk]
Collect the necessary contextual parameters from the user prompt or environment:
{project_id},{cluster_name},{location},{nodepool_name}, and{issue_time}.{mig_name}and{zone}: Name and zone of the managed instance group that backs{nodepool_name}, from the node pool'sinstanceGroupUrlsfield (see View node pools in a Standard cluster and Resource: NodePool). If{nodepool_name}or{mig_name}isn't already known from a failingSlice, find the affected partition, nodes, and backing MIG by following Verify the status of the nodes and the partitions.Time window: By default, query a 60-minute window
[{issue_time} - 30m, {issue_time} + 30m]({start_time}to{end_time}).
Step 1: Detect slice creation failures and MIG errors [Low Risk]
Inspect Slice status and partition nodes: Check the
Slicecustom resourceStatus.Conditionsfor aSliceCreationFailedstatus reason and identify the affected partitions, nodes, and{mig_name}by following the "Monitor the status of the Slice custom resource" and "Verify the status of the nodes and the partitions" sections of Use dynamic slicing with a custom scheduler, and Monitor the status of the slice.Query Cloud Logging for MIG errors: Once
{mig_name}is identified (or by narrowing the results to{mig_name}once known), run this Cloud Logging query to detect errors on the backing instance group manager across[{start_time}, {end_time}]:resource.type="gce_instance_group_manager" resource.labels.instance_group_manager_name="{mig_name}" severity>=ERROR timestamp >= "{start_time}" AND timestamp <= "{end_time}"
Findings:
If the
Slicestatus reportsSliceCreationFailedor the logs show instance group errors, proceed to Step 2.If no error logs match and the TPU
Slicestatus isACTIVE, rule out MIG instability and check workload configuration.
Step 2: Check MIG stability (status.isStable) [Low Risk]
Follow
Check whether a MIG is stable
to inspect the stability (status.isStable) and version target status
(status.versionTarget.isReached) of {mig_name}:
What the fields mean:
status.isStable: false: Changes are active or pending, or the MIG itself is being modified. Proceed to Step 3.status.versionTarget.isReached: false: At least one instance isn't running the target version yet (see Automatically apply VM configuration updates in a MIG). Proceed to Step 3.status.isStable: trueandstatus.versionTarget.isReached: true: No instances are undergoing or scheduled for changes (currentActionisNONEfor all instances), and the MIG itself isn't being modified. This rules out MIG instability. If theSliceis still inSliceCreationFailed, hand off togke-ai-troubleshooting-tpu-dynamic-slices-monitoring, or follow the "Create a Slice custom resource" and "Verify the status of the nodes and the partitions" sections of Use dynamic slicing with a custom scheduler.
Step 3: Find failed or stalled instance operations [Low Risk]
Direct the user to the "Check the status of managed instances" and "List
instance errors" sections of
View information about MIGs and managed instances
(include both section names and the document title) to inspect individual
instance states (currentAction and instanceStatus) and list the most recent
errors in {mig_name}:
If the errors show capacity or quota failures such as
ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILSorQUOTA_EXCEEDED, go to Step 5, item 2.Otherwise, proceed to Step 4 to check for node pool upgrade or auto-repair operations.
Step 4: Check node pool operations [Low Risk]
A MIG that is still changing instances can be the result of a node pool upgrade or repair:
Check node pool upgrades: Follow Check node pool upgrade status to list the cluster operations and find upgrade operations targeting
{nodepool_name}in[{start_time}, {end_time}]. Also review Upgrade your node pools for dynamic slicing upgrade requirements (required surge settings and deleting active super-slices before upgrading).If an upgrade operation is still running, go to Step 5, item 1 or item 3.
If an upgrade operation was cancelled, failed, or is incomplete, go to Step 5, item 4.
Check automated node repairs: Follow Get information about recent automated repair events to check for repair operations on
{nodepool_name}.If a node auto-repair operation is running, go to Step 5, item 1.
If no operation or error explains the unstable MIG: Go to Step 5, item 5 to contact Cloud Customer Care.
Step 5: Resolution [High Risk]
Guardrail: Don't modify GKE-managed instance groups or VMs directly through Compute Engine. Manage node pools through GKE.
Wait for an ongoing update or auto-repair to finish: If a node pool upgrade or automated repair is still making progress, the user can wait until the MIG is stable (
status.isStable: true) by following Check whether a MIG is stable.Resolve capacity or quota errors: When Step 3 shows
ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILSorQUOTA_EXCEEDED, rolling back an upgrade won't resolve the shortage. Follow Issue: Node pool creation fails due to insufficient resources and the "Insufficient quota to satisfy the TPU request" and "Insufficient TPU resources to satisfy the TPU request" sections of Troubleshoot TPUs in GKE.Cancel an in-progress node pool upgrade: If the user wants to stop an upgrade that is still running, follow Cancel a node pool upgrade. For dynamic slicing node pools, also check Upgrade your node pools for the required surge settings and deleting active super-slices before upgrading.
Resume or roll back a cancelled, failed, or incomplete node pool upgrade:
Follow the "Resume a node pool upgrade" or "Roll back a node pool upgrade" sections of Manually upgrade a cluster's control plane or node pools. As documented there, rollback applies if an in-progress upgrade was cancelled, the upgrade failed, or the upgrade is incomplete due to a maintenance window timing out (you can't roll back node pools once they have been successfully upgraded); alternatively, a cancelled or failed, partially completed upgrade can be resumed.
Afterwards, verify that the MIG is stable by following Check whether a MIG is stable.
Escalate unexplained MIG instability: If no node pool upgrade, repair operation, or capacity/quota error explains why
{mig_name}remains unstable, direct the user to Cloud Customer Care by following Get support.Verify node pool and slice recovery: After the instance group is stable (
status.isStable: true), follow the "Monitor the status of the Slice custom resource" and "Create a Slice custom resource" sections of Use dynamic slicing with a custom scheduler to verify that theSlicereaches theACTIVEstate. If theSlicestays inSliceCreationFailedafter the MIG stabilizes, check whether the retry annotation documented in "Create a Slice custom resource" is set on theSlice.
Files
- ATTRIBUTION.mdAdded by AutoGineer920 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md15.4 KiB
- references/attribution.md2.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/gke-ai-troubleshooting-tpu-slice-mig-stuck-updating · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download gke-ai-troubleshooting-tpu-slice-mig-stuck-updating.zip