Skip to content
New issue

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

PodVolumeBackup failed with the self-signed certificate minio as the backup storage #5502

Closed
ywk253100 opened this issue Oct 27, 2022 · 1 comment
Assignees
Labels
Milestone

Comments

@ywk253100
Copy link
Contributor

Setup the minio with self-signed certificate as the backup storage and config insecureSkipTLSVerify of the BSL as true.
Create a backup with restic, the Backup failed with errors

time="2022-10-27T06:00:07Z" level=error msg="Error backing up item" backup=velero/restic-03 error="pod volume backup failed: running backup, stderr=error getting snapshot id with error: error running command, stderr=Fatal: unable to open config file: Stat: Get \"https://minio.minio.svc:9000/velero/?location=\": x509: certificate signed by unknown authority\nIs there a repository at the following location?\ns3:https://minio.minio.svc:9000/velero/restic/default\n: exit status 1: error getting snapshot id with error: error running command, stderr=Fatal: unable to open config file: Stat: Get \"https://minio.minio.svc:9000/velero/?location=\": x509: certificate signed by unknown authority\nIs there a repository at the following location?\ns3:https://minio.minio.svc:9000/velero/restic/default\n: exit status 1" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/podvolume/backupper.go:223" error.function="github.com/vmware-tanzu/velero/pkg/podvolume.(*backupper).BackupPodVolumes" logSource="pkg/backup/backup.go:425" name=etcd0

The PodVolumeBackup:

apiVersion: velero.io/v1
kind: PodVolumeBackup
metadata:
  annotations:
    velero.io/pvc-name: etcd0-pv-claim
  creationTimestamp: "2022-10-27T06:00:05Z"
  generateName: restic-03-
  generation: 4
  labels:
    velero.io/backup-name: restic-03
    velero.io/backup-uid: 279ad4fe-623d-46c2-8a5e-33e01355556e
    velero.io/pvc-uid: 5315ee28-6f07-4288-81c9-56cfa4d42998
  name: restic-03-wghsj
  namespace: velero
  ownerReferences:
  - apiVersion: velero.io/v1
    controller: true
    kind: Backup
    name: restic-03
    uid: 279ad4fe-623d-46c2-8a5e-33e01355556e
  resourceVersion: "67935"
  uid: 5dfc392e-f278-4abd-acce-16acdd56a914
spec:
  backupStorageLocation: minio
  node: aks-agentpool-42398165-vmss000001
  pod:
    kind: Pod
    name: etcd0
    namespace: default
    uid: aa2d9048-32e1-45ea-b406-685761a242bf
  repoIdentifier: s3:https://minio.minio.svc:9000/velero/restic/default
  tags:
    backup: restic-03
    backup-uid: 279ad4fe-623d-46c2-8a5e-33e01355556e
    ns: default
    pod: etcd0
    pod-uid: aa2d9048-32e1-45ea-b406-685761a242bf
    pvc-uid: 5315ee28-6f07-4288-81c9-56cfa4d42998
    volume: etcd0-storage
  uploaderType: restic
  volume: etcd0-storage
status:
  completionTimestamp: "2022-10-27T06:00:07Z"
  message: |-
    running backup, stderr=error getting snapshot id with error: error running command, stderr=Fatal: unable to open config file: Stat: Get "https://minio.minio.svc:9000/velero/?location=": x509: certificate signed by unknown authority
    Is there a repository at the following location?
    s3:https://minio.minio.svc:9000/velero/restic/default
    : exit status 1: error getting snapshot id with error: error running command, stderr=Fatal: unable to open config file: Stat: Get "https://minio.minio.svc:9000/velero/?location=": x509: certificate signed by unknown authority
    Is there a repository at the following location?
    s3:https://minio.minio.svc:9000/velero/restic/default
    : exit status 1
  phase: Failed
  progress:
    bytesDone: 128020480
    totalBytes: 128020480
  startTimestamp: "2022-10-27T06:00:05Z"

Vote 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.

  • 👍 for "I would like to see this bug fixed as soon as possible"
  • 👎 for "There are more important bugs to focus on right now"
@qiuming-best
Copy link
Contributor

I've fixed it, if it still has problem, please reopen it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants