cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From serg38 <>
Subject [GitHub] cloudstack issue #1542: CLOUDSTACK-9379: Support nested virtualization at VM...
Date Mon, 21 Nov 2016 02:03:24 GMT
Github user serg38 commented on the issue:
    @rhytd @jburwell  @karuturi          test_nested_virtualization_vmware	Success	305.03
    The other tests fail due to environmental issues e.g. below. I think it is ready for merging
    2016-11-20 16:32:00,324 - CRITICAL - EXCEPTION: test_3d_gpu_support: ['Traceback (most
recent call last):\n', '  File "/usr/lib64/python2.7/unittest/", line 369, in run\n
   testMethod()\n', '  File "/marvin/tests/smoke/", line 316,
in test_3d_gpu_support\n    self.virtual_machine.add_nic(self.apiclient,\n',
'  File "/usr/lib/python2.7/site-packages/marvin/lib/", line 784, in add_nic\n    return
apiclient.addNicToVirtualMachine(cmd)\n', '  File "/usr/lib/python2.7/site-packages/marvin/cloudstackAPI/",
line 637, in addNicToVirtualMachine\n    response = self.connection.marvinRequest(command,
response_type=response, method=method)\n', '  File "/usr/lib/python2.7/site-packages/marvin/",
line 379, in marvinRequest\n    raise e\n', "Exception: Job failed: {jobprocstatus : 0, created
: u'2016-11-20T16:29:43+0000', cmd : u'org.apache.cloudstack.api.command.admin.vm.AddNicTo
 VMCmdByAdmin', userid : u'1575bde5-af3a-11e6-b333-06aa7801071a', jobstatus : 2, jobid : u'78b21bfa-bc82-4df6-ad54-67ef0899ceeb',
jobresultcode : 530, jobresulttype : u'object', jobresult : {errorcode : 530, errortext :
u'Unable to add NIC to VM[User|i-7-9-VM]: **Resource
[Host:1] is unreachable:** Host 1: Unable to start instance due to Unable to start  VM:a42c5549-c3c4-47b3-8e49-0785d1c2ef44
due to error in finalizeStart, not retrying'}, accountid : u'1575a6c7-af3a-11e6-b333-06aa7801071a'}\n"]

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message