Github user singalrahul commented on the pull request: https://github.com/apache/cloudstack/pull/1523#issuecomment-216230102 test_deploy_vm_userdata_MultiNic.py script is added for the verification of this Bug. It will verify that a user can deploy MultiNic VM when non-default nic does not have userdata service and can also update vm userdata. Before Fix, below was the result:- Test userdata update when non default nic is without userdata ... === TestName: test_deployvm_multiNic | Status : FAILED === FAIL ====================================================================== FAIL: Test userdata update when non default nic is without userdata ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/pmanthen/test_deploy_vm_userdata_MultiNic.py", line 183, in test_deployvm_multiNic self.fail("Failed to update userdata: %s" % e) AssertionError: Failed to update userdata: Execute cmd: updatevirtualmachine failed, due to: errorCode: 530, errorText:Service UserData is not supported in the network id=237 -------------------- >> begin captured stdout << --------------------- === TestName: test_deployvm_multiNic | Status : FAILED === [failed_plus_exceptions.txt](https://github.com/apache/cloudstack/files/245103/failed_plus_exceptions.txt) [results.txt](https://github.com/apache/cloudstack/files/245104/results.txt) [runinfo.txt](https://github.com/apache/cloudstack/files/245105/runinfo.txt) After the Fix:- Test userdata update when non default nic is without userdata for deploy and update ... === TestName: test_deployvm_multinic | Status : SUCCESS === ok ---------------------------------------------------------------------- Ran 1 test in 40.583s OK [results.txt](https://github.com/apache/cloudstack/files/245106/results.txt) [runinfo.txt](https://github.com/apache/cloudstack/files/245107/runinfo.txt)
--- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---