You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but the number count of ERRORS in velero restore get is 0
NAME BACKUP STATUS STARTED COMPLETED ERRORS WARNINGS CREATED SELECTOR
restore-mongo-data backup-2302 Completed 2024-03-15 09:42:05 +0000 UTC 2024-03-15 09:43:57 +0000 UTC 0 0 2024-03-15 09:42:05 +0000 UTC foundationservices.cloudpak.ibm.com=mongo-data
What did you expect to happen:
The velero restore get should show the number of errors correctly
The following information will help us better understand what's going on:
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"
The text was updated successfully, but these errors were encountered:
What steps did you take and what happened:
When I restore resources, data is not restored and I can see there is some error message in velero pod:
but the number count of ERRORS in
velero restore get
is 0What did you expect to happen:
The
velero restore get
should show the number of errors correctlyThe following information will help us better understand what's going on:
bundle-2024-03-25-11-24-39.tar.gz
Environment:
velero version
):velero client config get features
):kubectl version
):/etc/os-release
):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.
The text was updated successfully, but these errors were encountered: