qiuming-best
commented
2 years ago @matthiasritter how do you install velero? And whether have you compiled the velero bin by yourself?
Closed matthiasritter closed 1 year ago
qiuming-best
commented
2 years ago @matthiasritter how do you install velero? And whether have you compiled the velero bin by yourself?
matthiasritter
commented
2 years ago Hi @qiuming-best, we install velero via helm-chart (and terraform helm_release). I've got an M1-Mac and installed the velero-bin via "brew".
qiuming-best
commented
2 years ago @matthiasritter is it 100% occur when executing the above command?
I've tried in my own M1 Mac in AKS cluster, All going well.
matthiasritter
commented
2 years ago Hi @qiuming-best ,
yes it occur every time reproducable (same with my colleagues):
kubectl get backupstoragelocations.velero.io
NAME PHASE LAST VALIDATED AGE DEFAULT
default Available 19s 12d truek get backupstoragelocations.velero.io default -oyaml
apiVersion: velero.io/v1
kind: BackupStorageLocation
metadata:
annotations:
helm.sh/hook: post-install,post-upgrade,post-rollback
helm.sh/hook-delete-policy: before-hook-creation
creationTimestamp: "2022-07-19T14:35:36Z"
generation: 95827
labels:
app.kubernetes.io/instance: velero
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: velero
helm.sh/chart: velero-2.30.1
name: default
namespace: velero
resourceVersion: "143367598"
uid: 12345678900ß
spec:
accessMode: ReadWrite
config:
bucket: velero-backups
prefix: ""
resourceGroup: myresourcegroup
storageAccount: backupstorageaccount
subscriptionId: 12345678901234567890
default: true
objectStorage:
bucket: velero-backups
provider: azure
status:
lastSyncedTime: "2022-08-01T05:16:29Z"
lastValidationTime: "2022-08-01T05:16:30Z"
phase: Availablevelero backup-location get --default -o yaml
unexpected fault address 0x360808085a175a75
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x2 addr=0x360808085a175a75 pc=0x1007826c0]
....@matthiasritter could you provide the output of command velero version for me ?
matthiasritter
commented
2 years ago @qiuming-best sure
velero version Client: Version: v1.9.0 Git commit: - Server: Version: v1.9.0
qiuming-best
commented
2 years ago @matthiasritter thanks, is there no Git commit ID shown by the output?
matthiasritter
commented
2 years ago @qiuming-best nope, only this:
velero version
Client:
Version: v1.9.0
Git commit: -
Server:
Version: v1.9.0@matthiasritter could you retry with the link velero bin instead of using the brew installation way?
matthiasritter
commented
2 years ago @qiuming-best thanks, with this bin it work
jbpin
commented
2 years ago I had the same issue with velero backup get -o json it work with the link.
Edit:
I've install velero with brew as well
Lyndon-Li
commented
2 years ago Looks like the Velero image is from 1.8 code but compiled with go 1.18, so it should be the same with issue #4942:
However, I don't know how the problem connects to brew install.
stale[bot]
commented
1 year ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale[bot]
commented
1 year ago Closing the stale issue.
What steps did you take and what happened: I executed the following command
velero backup-location get --default -o yamlor I executed the following commandvelero backup-location get --default -o jsonThe command failed with the error:What did you expect to happen: To see the actuall configuration in yaml
The following information will help us better understand what's going on: We are using:
Environment:
velero version):Client: Version: v1.9.0 Git commit: - Server: Version: v1.9.0velero client config get features):velero client config get features features: <NOT SET>kubectl version):kubectl version WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version. Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:21:56Z", GoVersion:"go1.18.4", Compiler:"gc", Platform:"darwin/arm64"} Kustomize Version: v4.5.4 Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.14", GitCommit:"767d382613a87705d5ee3e6b1adf6c041089f27f", GitTreeState:"clean", BuildDate:"2022-06-21T17:11:30Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}/etc/os-release): UbuntuVote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.