VM was being created with accountid and also project. By doing
this create vm or any other resource will fail. Only specify
project in which resource is created.
component.test_project_limits.TestMaxProjectNetworks.test_maxAccountNetworks tries to create multiple guest networks in an project of account which is not possible in basic zone as there is only one guest network allowed per zone in basic zone setup.
Hence removing the tags basic and sg so that this test case won't be picked up to run on basic zone setup.
case which is invalid for the basic zone
TestRouterRestart.test_01_restart_network_cleanup test scenario is invalid for basic zone. The test case tries to restart the Router assigned to individual account but in basic zone, there is only one router i.e of shared network and there is only one guest(shared) network per zone. Hence the API fails to list the router of the individual account.
More over, we will not try to restart the Router of the shared network because it is used by many accounts and restarting it may affect the execution of other test cases.
Fixed following test cases:
1) test_01_volume_from_snapshot
2) test_03_snapshot_detachedDisk
3) test_07_template_from_snapshot
All three test cases are running successfully on XenServer but test cases (01 and 07) failing on KVM due to a common issue.
Product defect logged for this: https://issues.apache.org/jira/browse/CLOUDSTACK-5097
test_03 is running ok on KVM too, the problem was - disk was not getting detached because it was not unmounted before detaching. Added code to unmount the disk.
Signed-off-by: Girish Shilamkar <girish@clogeny.com>
There were two module files with same name and
is creating confusion while reporting the test results.
Renamed them prefixing them with mem\cpu
Signed-off-by: Santhosh Edukulla <Santhosh.Edukulla@citrix.com>
Signed-off-by: SrikanteswaraRao Talluri <talluri@apache.org>
test_deployVmSharedNetworkWithoutIpRange creates a shared network
without start and end ip. This is no longer permitted and creation
of shared network will fail with error "insufficient capacity". So
remove this test which is invalid.
Signed-off-by: Girish Shilamkar <girish@clogeny.com>
Now VPN connection can be created as "passive", which would enable the ability
of remote peer initiate the connection. So it's possible for VPC VR to
establish the connection to another VPC VR of CloudStack.
Test case also included.
The test case would create 2 vpcs and using VPN to connect them.
CLOUDSTACK-702: Test for verifying ip alias after VR stop start
1.Deploy vm in new cidr which will create ip alias on existing VR
Stop,start VR and verify ip alias
Conflicts:
test/integration/component/maint/test_multiple_ip_ranges.py
Signed-off-by: SrikanteswaraRao Talluri <talluri@apache.org>