You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a very extreme case where the kk backup etcd script may erroneously delete / directory files when the node has no space to create directories (i.e not even 4096K).
Suggest using the latest version:
Binary downloads of the latest kk can be found on the Releases page.
Or
Download the latest kk by the following command
curl -sSL https://get-kk.kubesphere.io | sh -
And for the existing cluster installed by KubeKey command (kk), here is a solution.
manually editing the script:
$ vi /usr/local/bin/kube-scripts/etcd-backup.sh
modify the script like the below:
add set -o xxx at the beginning of the script
replace the ; after the cd command with && in the last line
We've unfortunately encounted with this bug. The root partition is mounted with option 'error=remount-ro', and accidently triggered it. So mkdir -p failed, cd failed, / is deleted.
Our data is shared with NAS and mounted under /. And they're all GONE.
What is version of KubeKey has the issue?
v3.0.1, v3.0.0, v2.3.0, v2.2.2, v2.2.1, v2.2.0, v2.1.1, v2.1.0, v2.0.0, v1.2.1, v1.2.0, v1.1.1, v1.1.0, v1.0.1
What is your os environment?
none
KubeKey config file
No response
A clear and concise description of what happend.
There is a very extreme case where the kk backup etcd script may erroneously delete
/
directory files when the node has no space to create directories (i.e not even 4096K).Suggest using the latest version:
Binary downloads of the latest kk can be found on the Releases page.
Or
Download the latest kk by the following command
And for the existing cluster installed by KubeKey command (kk), here is a solution.
modify the script like the below:
set -o xxx
at the beginning of the script;
after thecd
command with&&
in the last lineHere is an example:
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: