Recover a failed upgrade in Google Distributed Cloud
Stay organized with collections
Save and categorize content based on your preferences.
Occasionally, Google Distributed Cloud may run into conditions where you need to
start an upgrade over again, or fix an error condition to complete the upgrade
successfully. The following conditions may occur when upgrading clusters. Try
to complete the cluster upgrade as noted with the condition.
Recover admin, hybrid, and standalone cluster upgrades
Admin, hybrid, and standalone clusters are all upgraded with the bmctl upgrade
command.
If your upgrade doesn't complete successfully, check the following conditions
and try the upgrade again.
bmctl fails to parse the config file due to a mistake. Fix the config file
and rerun the command.
bmctl fails to bootstrap the temporary cluster. Retry the command.
the log files indicate that the upgrade failed a preflight check. Correct the preflight condition, or force
the upgrade.
the upgrade took too long (more than 30 minutes) or timed out. Retry the
upgrade command.
If your upgrade doesn't complete successfully, check the following conditions
and try the upgrade again.
Preflight check failed. Check the preflight check log and fix the
corresponding error.
You may need to construct a new preflight custom resource following these instructions
and apply it to the cluster. Check that the
triggered preflight passes, and that the cluster reconciler
picks up the latest passing state.
What's next
If you need additional assistance, reach out to
Cloud Customer Care.
You can also see
Getting support for more information about support resources, including the following:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["Occasionally, Google Distributed Cloud may run into conditions where you need to\nstart an upgrade over again, or fix an error condition to complete the upgrade\nsuccessfully. The following conditions may occur when upgrading clusters. Try\nto complete the cluster upgrade as noted with the condition.\n\nRecover admin, hybrid, and standalone cluster upgrades\n\nAdmin, hybrid, and standalone clusters are all upgraded with the [`bmctl upgrade`\ncommand](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/upgrade).\n\nIf your upgrade doesn't complete successfully, check the following conditions\nand try the upgrade again.\n\n- `bmctl` fails to parse the config file due to a mistake. Fix the config file and rerun the command.\n- `bmctl` fails to bootstrap the temporary cluster. Retry the command.\n- the log files indicate that the upgrade failed a [preflight check](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/preflight). Correct the preflight condition, or force the upgrade.\n- the upgrade took too long (more than 30 minutes) or timed out. Retry the upgrade command.\n\nRecover user cluster upgrades\n\nUser clusters are [upgraded from an associated admin cluster](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/upgrade)\nwith the `kubectl apply` command.\n\nIf your upgrade doesn't complete successfully, check the following conditions\nand try the upgrade again.\n\n- Preflight check failed. Check the preflight check log and fix the corresponding error.\n- You may need to construct a new preflight custom resource [following these instructions](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/preflight#re-enabling_preflight_checks) and apply it to the cluster. Check that the triggered preflight passes, and that the cluster reconciler picks up the latest passing state.\n\nWhat's next\n\nIf you need additional assistance, reach out to\n\n[Cloud Customer Care](/support-hub).\nYou can also see\n[Getting support](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support) for more information about support resources, including the following:\n\n- [Requirements](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#intro-support) for opening a support case.\n- [Tools](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#support-tools) to help you troubleshoot, such as your environment configuration, logs, and metrics.\n- Supported [components](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#what-we-support)."]]
