yijing
yijing
Seeing this error again after restore datafile and volume-snapshot backup of mongo-4.4 after upgrade kb from 0.7.2 to 0.8.0
starrocks also encountered the same error, the pod restart 2 times during cluster restart, causing the ops failed, while the cluster will eventually running https://github.com/apecloud/kubeblocks/actions/runs/9706734671/job/26791580145
When restart greptime, encoutered the same problem ➜ ~ kbcli version Kubernetes: v1.27.3-gke.100 KubeBlocks: 0.8.0-beta.13 kbcli: 0.8.0-beta.13 ``` greptime-hbmgfp-frontend-0 0/1 CrashLoopBackOff 6 (31s ago) 6m34s greptime-hbmgfp-frontend-1 0/1 CrashLoopBackOff 6 (36s...
Still failed when restart with kb upgraded from 0.7.2 to 0.8.0-beta.44 ``` `kbcli cluster restart greptime-khludk --auto-approve --components frontend --namespace default ` OpsRequest greptime-khludk-restart-s6vqp created successfully, you can view the...
failed again when create greptime on 0.8.1-beta.5 ``` apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: greptime-qyfpto namespace: default spec: clusterDefinitionRef: greptimedb clusterVersionRef: greptimedb-0.3.2 terminationPolicy: DoNotTerminate componentSpecs: - name: frontend componentDefRef: frontend...
Tried again, the addons were finally installed, but the status in kbcli addon list is still Failed, the status should sync with the actual pod status ``` ➜ ~ kbcli...
I expect when pod status is running, addon status should also changed to enabled instead of failed
The pod recovery after 8 restarts ``` pulsarcluster-bookies-4 2/2 Running 8 (15m ago) 32m ```
This is still failing on 0.7.0-beta.4