[
https://issues.apache.org/jira/browse/CLOUDSTACK-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749920#comment-13749920
]
ASF subversion and git services commented on CLOUDSTACK-4452:
-------------------------------------------------------------
Commit 02e7630f1cf218b1436a71a42623a7bf790d98e7 in branch refs/heads/master
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=02e7630 ]
CLOUDSTACK-4452: Cleaning up the is_snapshot_on_nfs utility
- Pass in config and determine the mgmtsvr credentials
- remove the dir_paths param which is not reqd.
- pass all entities as uuids and convert to ids within the method
Signed-off-by: Prasanna Santhanam <[email protected]>
> test_snapshots.py - The method used to check whether snapshot exists on
> secondary storage is wrong
> --------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4452
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4452
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
> Affects Versions: 4.2.0
> Reporter: Gaurav Aradhye
> Assignee: Gaurav Aradhye
> Fix For: 4.2.0
>
>
> Following test case failing due to this:
> 1. test_01_createVM_snapshotTemplate
> 2. test_02_snapshot_data_disk
> 3. test_04_delete_snapshot
> The method (is_snapshot_on_nfs) used to check whether snapshot exists on
> secondary storage is wrong. Currently it's trying to match the name of
> snapshot present on the storage with the UUID of snapshot. There's no
> relation between the name of snapshot on storage and it's UUID or snapshot
> ID. Hence it shoould only check if the snapshot is present in the directory
> --> snapshots/account/volume/directory/ in SSVM
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
