[ https://issues.apache.org/jira/browse/CLOUDSTACK-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235001#comment-15235001 ]
ASF subversion and git services commented on CLOUDSTACK-9215: ------------------------------------------------------------- Commit c3e26bf367be863e90cdaef22a94bf1fd5ab45d6 in cloudstack's branch refs/heads/master from [~williamstev...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c3e26bf ] Merge pull request #1316 from sanju1010/vmxnet3 [CLOUDSTACK-9215]Test to verify vm deployment in vpc tier if nic type is Vmxnet3Please check bug CLOUDSTACK-9215 for more details. Test Results: ========== Test to create vpc tier with nic type as Vmxnet3 ... === TestName: test_01_create_tier_Vmxnet3 | Status : SUCCESS === ok ---------------------------------------------------------------------- Ran 1 test in 591.630s OK * pr/1316: New marvin test to validate CLOUDSTACK-9215 Bug-Id: CLOUDSTACK-9215 Signed-off-by: Will Stevens <williamstev...@gmail.com> > Marvin test to check vm deployment in vpc tier if nic type is vmxnet3 > --------------------------------------------------------------------- > > Key: CLOUDSTACK-9215 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9215 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware > Reporter: Sanjeev N > Assignee: Sanjeev N > > Marvin test to check vm deployment in vpc tier if nic type is vmxnet3. > If sytemvm nic type is vmxnet3, debian os takes little more time to discover > the nic after hot plugin compared to nic type E1000. So vm deployment fails. > Adding new test to validate this functionality with nic type vmxnet3. > Steps followed in the test: > 1.Set systemvm.nic.type to Vmxnet3 and restart MS > 2.Create VPC > 3.Create Tier > 4.Deploy one guest vm and make sure no issues in vm deployment > 5.Reset the nic type to old value -- This message was sent by Atlassian JIRA (v6.3.4#6332)