-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Issues: vmware-tanzu/velero
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Micro service data mover restore's BYTES DONE is not equal to TOTAL BYTES in status
area/datamover
Restore
#8232
opened Sep 19, 2024 by
blackpiglet
Micro-service datamover backup recovery issue
area/datamover
#8231
opened Sep 19, 2024 by
blackpiglet
File system restore cannot work in PSA enabled Kubernetes cluster
1.16-candidate
downstream-integration
The issue originated from downstream integration
PodVolume
#8229
opened Sep 19, 2024 by
ywk253100
FailedValidation creating schedule with CRON_TZ
Candidate for close
Issues that should be closed and need a team review before closing
#8224
opened Sep 18, 2024 by
vmaglietta
Data mover --- node selection by storage class
area/datamover
kind/requirement
#8223
opened Sep 18, 2024 by
Lyndon-Li
[Kopia] Backup partially failing with timeout error after 24 hours despite default timeout of 4h
Kopia
PodVolume
#8220
opened Sep 16, 2024 by
navilg
Velero command not throwing and error when schedule hasn't been correctly defined
Area/CLI
related to the command-line interface
#8214
opened Sep 12, 2024 by
jeremyvdveen
time="2024-09-12T09:56:32Z" level=warning msg="Velero node agent not found; pod volume backups/restores will not work until it's created" logSource="pkg/cmd/server/server.go:567".
Needs info
Waiting for information
#8212
opened Sep 12, 2024 by
Srija-ravi
Allow resource status restore in a more granular way
1.16-candidate
Needs Design
#8204
opened Sep 10, 2024 by
shubham-pampattiwar
Velero not automatically detecting aws s3 region for buckets anymore after updating to v1.14.1
Area/Cloud/AWS
#8200
opened Sep 10, 2024 by
thomaspeitz
Data mover Micro Service -- support NFS/local-volume/host-path volume as target BSL
area/datamover
backlog
#8190
opened Sep 6, 2024 by
Lyndon-Li
Restore Data Movement Node Selection
area/datamover
kind/requirement
#8186
opened Sep 4, 2024 by
MuriloCouceiro
Allow user to remove host path mount for node-agent
area/datamover
backlog
#8185
opened Sep 4, 2024 by
Lyndon-Li
Update conflict should be handled when restoring the "Status"
1.16-candidate
Restore
#8184
opened Sep 4, 2024 by
ywk253100
The "managedFields" patching logic doesn't apply to "namespace" resources during the restoration
backlog
Restore
#8183
opened Sep 4, 2024 by
ywk253100
Restore finalizing should not run if the async restore operation is failed/cancelled
Needs investigation
Restore
#8182
opened Sep 4, 2024 by
Lyndon-Li
Impossible to restore PVC using CSI data mover on OKD cluster
area/datamover
#8178
opened Sep 2, 2024 by
vincmarz
Since velero version 1.14 we are getting error of expired token for backing up data using datamover
Area/Cloud/AWS
Needs info
Waiting for information
#8173
opened Sep 1, 2024 by
dharanui
Backup with --move-snapshot-data fails to restore
Needs info
Waiting for information
#8171
opened Aug 30, 2024 by
darnone
AWS secrets may be exposed when running repository/config/aws tests in the CI workflows
#8168
opened Aug 30, 2024 by
mpryc
ChangeStorageClassAction doesn't affect VolumeType of restored volume
limitation
native-snapshot
#8164
opened Aug 29, 2024 by
Lirt
Cleanup of Leaked Snapshot due to Velero Pod Restart while backup is In-Progress
1.16-candidate
Area/CSI
Related to Container Storage Interface support
Bug
Needs investigation
#8160
opened Aug 29, 2024 by
mayankagg9722
Post hook command is executed before the Kopia snapshot is completed
1.16-candidate
backlog
#8159
opened Aug 29, 2024 by
QuentinBtd
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.