We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when execute restore , the status is null,actual because cluster name is wrong,it should be nebula-ent-sc, but i set as nebula
nebula-ent-sc
nebula
restore.yaml:
apiVersion: apps.nebula-graph.io/v1alpha1 kind: NebulaRestore metadata: name: restore1 namespace: nebula-ent-sc spec: br: clusterName: nebula backupName: "BACKUP_2023_08_07_07_52_28" concurrency: 5 s3: region: "us-west-2" bucket: "test-qa" endpoint: "http://192.168.8.202:32000" secretName: "aws-s3-secret"
from the follow logs ,i can not realize the problem is cluster name is wrong, can we give specific tips? logs in nebula-operator is:
cluster name is wrong
I0807 08:11:20.678980 1 nebula_restore_controller.go:84] Finished reconciling NebulaRestore [nebula-ent-sc/restore1], spendTime: (166.294µs) I0807 08:12:53.590898 1 nebula_restore_controller.go:98] Start to reconcile NebulaRestore I0807 08:12:53.598794 1 nebularestore.go:87] NebulaRestore [nebula-ent-sc/restore1] updated successfully I0807 08:12:53.598887 1 nebula_restore_manager.go:791] generate restored nebula cluster name successfully I0807 08:12:53.602660 1 nebula_restore_controller.go:84] Finished reconciling NebulaRestore [nebula-ent-sc/restore1], spendTime: (11.805839ms) I0807 08:12:53.602810 1 nebula_restore_controller.go:98] Start to reconcile NebulaRestore I0807 08:12:53.608327 1 nebula_restore_controller.go:84] Finished reconciling NebulaRestore [nebula-ent-sc/restore1], spendTime: (5.549076ms) I0807 08:18:35.367752 1 nebula_restore_controller.go:98] Start to reconcile NebulaRestore I0807 08:18:35.375987 1 nebula_restore_controller.go:84] Finished reconciling NebulaRestore [nebula-ent-sc/restore1], spendTime: (8.379745ms) ...without others...
restore detail log:
# kubectl -n nebula-ent-sc get rt restore1 -oyaml apiVersion: apps.nebula-graph.io/v1alpha1 kind: NebulaRestore metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"apps.nebula-graph.io/v1alpha1","kind":"NebulaRestore","metadata":{"annotations":{},"name":"restore1","namespace":"nebula-ent-sc"},"spec":{"br":{"backupName":"BACKUP_2023_08_07_07_52_28","clusterName":"nebula","concurrency":5,"s3":{"bucket":"test-qa","endpoint":"http://192.168.8.202:32000","region":"us-west-2","secretName":"aws-s3-secret"}}}} creationTimestamp: "2023-08-07T08:12:56Z" generation: 1 name: restore1 namespace: nebula-ent-sc resourceVersion: "4843256" uid: c6cf12b4-e74b-4595-8688-e967a9198ef9 spec: br: backupName: BACKUP_2023_08_07_07_52_28 clusterName: nebula concurrency: 5 s3: bucket: test-qa endpoint: http://192.168.8.202:32000 region: us-west-2 secretName: aws-s3-secret status: clusterName: ng7jnz timeStarted: "2023-08-07T08:12:53Z"
Your Environments (required)
nebula-ent-sc-rc镜像: reg.vesoft-inc.com/rc/nebula-storaged-ent:v3.5.0-sc operator镜像是:reg.vesoft-inc.com/cloud-dev/nebula-operator:snap-1.4 nebula-agent镜像:reg.vesoft-inc.com/cloud-dev/nebula-agent:3.5.1-sc br-ent镜像:image: reg.vesoft-inc.com/cloud-dev/br-ent:v3.5.1
The text was updated successfully, but these errors were encountered:
#238
Sorry, something went wrong.
No branches or pull requests
when execute restore , the status is null,actual because cluster name is wrong,it should be
nebula-ent-sc
, but i set asnebula
restore.yaml:
from the follow logs ,i can not realize the problem is
cluster name is wrong
, can we give specific tips?logs in nebula-operator is:
restore detail log:
Your Environments (required)
nebula-ent-sc-rc镜像: reg.vesoft-inc.com/rc/nebula-storaged-ent:v3.5.0-sc
operator镜像是:reg.vesoft-inc.com/cloud-dev/nebula-operator:snap-1.4
nebula-agent镜像:reg.vesoft-inc.com/cloud-dev/nebula-agent:3.5.1-sc
br-ent镜像:image: reg.vesoft-inc.com/cloud-dev/br-ent:v3.5.1
The text was updated successfully, but these errors were encountered: