Dave Garbus created CLOUDSTACK-8691:
---------------------------------------
Summary: deployVirtualMachine should not error when userdata is
provided if at least one NIC supports it
Key: CLOUDSTACK-8691
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8691
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API
Affects Versions: 4.5.1
Environment: CentOS 6.X
Reporter: Dave Garbus
Priority: Critical
In our environment, we assign VMs a default NIC without the userdata service,
however, we also assign a secondary network that has the userdata service
enabled. In previous releases, and confirmed in the issue below, the API simply
warned about the default NIC not supporting userdata but continued to go on to
create the virtual machine.
https://issues.apache.org/jira/browse/CLOUDSTACK-4630?focusedCommentId=13770148&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13770148
As of 4.5.1, The API completely errors out and does not create the VM, even
though one of the NICs supports the userdata service. I can get around this
behavior by calling deployVirtualMachine with 'startvm' set to false, and then
a call to updateVirtualMachine with userdata=<my userdata>. Of course, this
breaks the automation that we have in place.
I really don't understand why the API would fail to create the VM as long as
one of the NICs supported the userdata service. This seems like a regression
from the previous releases and should be fixed. Here is the issue in which the
change was made:
https://issues.apache.org/jira/browse/CLOUDSTACK-6748
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
