Troubleshooting updates

What to check if updates fail.

The standard update procedure is described on the page How updates occur in open and closed loops. Before looking for a crash, make sure that the transition between versions is allowed: Update version map. For release policy and version support, see release policy.

The new version does not appear in the GUI #

If the version is listed as available for migration on the version map, but it is not in the GUI after waiting, save the kubectl output (see below) and contact support.

Update freezes #

• Identify on the dashboard the stage that remains in progress (yellow): shturval-update, removing legacy services, shturval-node-config, updating Kubernetes or updating platform system services.
• If the stage is gray, it has not yet been initialized or may be skipped; check the previous yellow stage and the logs of the corresponding component.
• If a stage remains yellow for a long time, click on the stage icon to get more detailed information about the conditions of the service or nodes. If this information is not enough, check the logs of the component of this stage and associated system services.
• Check the network connection to the Registry;

Checking update status (kubectl) #

When updating via GUI or automatically, the status can be checked via kubectl:

# List of update channels
kubectl get shturvalupdatechannel -A

# Channel details
kubectl describe shturvalupdatechannel <name> -n <namespace>

If the mirror update freezes, restarting the channel can help pick up the new version:

kubectl -n <namespace> rollout restart deployment shturval-update-channel