You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/06 13:09:25 UTC
[jira] [Commented] (CLOUDSTACK-9215) Marvin test to check vm
deployment in vpc tier if nic type is vmxnet3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228108#comment-15228108 ]
ASF GitHub Bot commented on CLOUDSTACK-9215:
--------------------------------------------
Github user sanju1010 commented on the pull request:
https://github.com/apache/cloudstack/pull/1316#issuecomment-206313506
Squashed changed into single commit and addressed all the review comments and also posted test run results after making changes. Can somebody please merge this PR?
> 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)