Changed error message when snapshot is not on secondary when trying to perform download #12462
+3
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, when trying to download a snapshot that is in primary storage, the error message
Snapshot not foundis shown, which may lead users into thinking that the snapshot does not exist in any storage anymore. This PR changes the message toSnapshot not found in any secondary storage. The snapshot may be on primary storage, where it cannot be downloaded.Types of changes
Feature/Enhancement Scale
How Has This Been Tested?
A VM was created to perform the tests. After that
Global Settingstab was accessed and the configurationsnapshot.backup.to.secondarywas set tofalse. After this change, I took a volume snapshot and tried to download it, and it was possible to validate that the shown message was changed.