[jira] [Created] (CLOUDSTACK-6216) [Automation] test_secondary_storage suite from BVT will always fail if it is run on an already deployed zone.

["Gaurav Aradhye (JIRA)" <ji...@apache.org>]

Gaurav Aradhye created CLOUDSTACK-6216:
------------------------------------------

             Summary: [Automation] test_secondary_storage suite from BVT will always fail if it is run on an already deployed zone.
                 Key: CLOUDSTACK-6216
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6216
             Project: CloudStack
          Issue Type: Test
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Automation
    Affects Versions: 4.4.0
            Reporter: Gaurav Aradhye
            Assignee: Gaurav Aradhye
             Fix For: 4.4.0


[Automation] test_secondary_storage suite from BVT will always fail if it is run on an already deployed zone.

setUp method has following statements:

 def setUp(self):
        self.apiclient = self.testClient.getApiClient()
        self.cleanup = []
        # Get Zone and pod
        self.zones = []
        self.pods = []
        for zone in self.config.zones:
            cmd = listZones.listZonesCmd()
            cmd.name = zone.name
            z = self.apiclient.listZones(cmd)
            if isinstance(z, list) and len(z) > 0:
                self.zones.append(z[0].id)
            for pod in zone.pods:
                podcmd = listPods.listPodsCmd()
                podcmd.zoneid = z[0].id
In this method zone name is taken from the config file for listing the zones. However if this script is run on an already deployed zone and if we don't change the zone name in the config file as per the deployment then the listZones(cmd) will return an empty list. 
In this method there is no assertion to check for the empty list response. It only checks whether the response is a list and its lenth > 0 . We should fail the script if the list is empty. This particular check is missing inside the setUp method.



--
This message was sent by Atlassian JIRA
(v6.2#6252)