[
https://issues.apache.org/jira/browse/CLOUDSTACK-8723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681590#comment-14681590
]
ASF GitHub Bot commented on CLOUDSTACK-8723:
--------------------------------------------
Github user nitt10prashant commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/675#discussion_r36731289
--- Diff: test/integration/testpaths/testpath_usage.py ---
@@ -2879,6 +2882,60 @@ def test_07_positive_tests_usage(self):
# aggregation period and current period will give the network usage
return
+ @attr(tags=["advanced", "basic"], required_hardware="false")
+ def test_08_checkNewVolumein_listUsageRecords(self):
+ """ Test case to check if new volume crated after
+ restore VM is listed in listUsageRecords
+ # 1. Launch a VM
+ # 2. Restore the VM
+ # 3. Check if the new volume created is listed in listUsageRecords
API
+ """
+
+ # Step 1
+ vm_cluster = VirtualMachine.create(
+ self.userapiclient,
+ self.testdata["small"],
+ templateid=self.template.id,
+ accountid=self.account.name,
+ domainid=self.account.domainid,
+ serviceofferingid=self.service_offering.id,
+ zoneid=self.zone.id,
+ )
+
+ volumes_root_list = list_volumes(
+ self.apiclient,
+ virtualmachineid=vm_cluster.id,
+ type='ROOT',
+ listall=True
+ )
--- End diff --
use validate list
> Verify API call "listUsageRecords" returns usage of new volume created after
> restore VM
> ---------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8723
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8723
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
> Affects Versions: 4.2.1
> Reporter: Priti Sarap
> Fix For: 4.2.1
>
>
> After restoring a running VM current ROOT disk gets destroyed and new ROOT
> disk gets created.
> This testcase is to check if volume usage of this newly created volume is
> listed in listUsageRecords API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
