[
https://issues.apache.org/jira/browse/CLOUDSTACK-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229875#comment-15229875
]
ASF GitHub Bot commented on CLOUDSTACK-9215:
--------------------------------------------
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1316#issuecomment-206751818
No, you are right. I no longer have that 'hardware' so I can rerun the test
but as I stated earlier the test was basing itself on an exception not being
throw at the time I did the test and therefore not as useful as would be
expected. The test has improved but I have no longer access to the virtualised
environment in which I ran it.
However; this is a test, not production code. What do you want from the
test other then the test writer being able to use it to verify ACS? Unless
testcode can harm production environments I'd say merge @swill @wilderrodrigues
@remibergsma @bhaisaab
> 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)
