etcd snapshots showing 0B size in the Rancher UI
This document (000021447) is provided subject to the disclaimer at the end of this document.
Environment
Situation
Resolution
kubectl get lease -n kube-system rke2-etcd -o jsonpath='{.spec.holderIdentity}' | xargs -I {} kubectl patch lease -n kube-system --patch='{"spec":{"holderIdentity":"{}"}}' --type=merge rke2; kubectl get lease -n kube-system -o custom-columns='name:.metadata.name,holder:.spec.holderIdentity' | grep rke2After this is done, if the rke2 or rke2-etcd ConfigMap objects have an annotation with a differing holderIdentity value, please modify that to match as well.
After the workaround is implemented, please wait some time for the snapshots to reconcile.
Ultimately, the solution will be to upgrade to the version where this bug is fixed.
Cause
kubectl get cm -n kube-system rke2 -o yaml | grep holderIdentity kubectl get cm -n kube-system rke2-etcd -o yaml | grep holderIdentity kubectl get lease -n kube-system rke2 kubectl get lease -n kube-system rke2-etcd
This is a known bug: https://github.com/rancher/rke2/issues/5866
Additional Information
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000021447
- Creation Date: 09-May-2024
- Modified Date:01-Jun-2024
-
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com