Recuperar um upgrade com falha no Google Distributed Cloud
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Às vezes, o Google Distributed Cloud pode se deparar com condições em que você precisa
iniciar um upgrade novamente ou corrigir uma condição de erro para concluir
o upgrade. As condições a seguir podem ocorrer ao fazer upgrade dos clusters. Tente
concluir o upgrade do cluster, conforme indicado pela condição.
Se o processo não for concluído, verifique as condições a seguir
e tente novamente.
Falha na verificação de simulação. Verifique o registro da verificação de simulação e corrija o
erro correspondente.
Talvez seja necessário criar um novo recurso personalizado de simulação seguindo estas instruções
e aplicá-lo ao cluster. Verifique se a
simulação acionada passa e se o reconciliador de cluster
obtém o estado de passagem mais recente.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2024-11-22 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)."]]
