[
https://issues.apache.org/jira/browse/CLOUDSTACK-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021876#comment-14021876
]
Koushik Das commented on CLOUDSTACK-6708:
-----------------------------------------
integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure
is not yet fixed as part of this. This test is based on simulator mocks, which
can be scoped to a zone, pod, cluster or host. The mock gets executed for any
test that targets the specific host for which mock is defined. Due to this,
tests using mock needs to be executed in sequence otherwise it may interfere
with other tests and cause random failures. The current test framework always
executes tests in parallel and needs to be fixed to execute selective tests in
sequence.
I will create a separate bug for it.
> [Automation]: Few suites were failing on simulator run
> ------------------------------------------------------
>
> Key: CLOUDSTACK-6708
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6708
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Reporter: Santhosh Kumar Edukulla
> Assignee: Santhosh Kumar Edukulla
>
> integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure
> integration.smoke.test_hosts.TestHosts.test_01_clusters
> integration.smoke.test_network.TestDeleteAccount.test_delete_account
> integration.smoke.test_network.TestPublicIP.test_public_ip_admin_account
> integration.smoke.test_network.TestReleaseIP.test_releaseIP
> integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_08_migrate_vm
> integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm
--
This message was sent by Atlassian JIRA
(v6.2#6252)
