cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajani Karuturi (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8691) deployVirtualMachine should not error when userdata is provided if at least one NIC supports it
Date Mon, 03 Aug 2015 09:48:05 GMT


Rajani Karuturi commented on CLOUDSTACK-8691:

[~dgarbus], Thanks for the detailed report. I really like it.
[~bhaisaab], Any chance you could take a look? As far as I can see, It came from the below
commit 24435dd6bc2424da18277ca00229d1d3bb0ec284
Author:     Rohit Yadav <>
AuthorDate: Thu Apr 16 16:51:02 2015 +0530
Commit:     Rohit Yadav <>
CommitDate: Thu Apr 16 17:28:20 2015 +0530

    server: NPE checks and improved case checking

    - pool allocation checks for both root and data disks
    - NPE checks to not add null object in collection or try to migrate null VM
    - HA work tries need to increment and be given up when max retries are crossed
    - VM creation should check IP address format for IPv4 and IPv6
    - If userdata is not supported by a network, then fail early if userdata, ssh key,
      or password enabled template is passed/used

    Signed-off-by: Rohit Yadav <>

> deployVirtualMachine should not error when userdata is provided if at least one NIC supports
> -----------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-8691
>                 URL:
>             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
>              Labels: userdata
> 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.
> 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:
> Steps to reproduce:
> 1. Create two networks in CloudStack, one with userdata service enabled, and one without.
> 2. Use deployVirtualMachine API call to create a virtual machine with both networks as
well as userdata. The first (default) network should be the one without the userdata service
and the second network should be the userdata-enabled network.
> 3. The API should present the following error: {{Error: Unable to deploy VM as UserData
is provided while deploying the VM, but there is no support for UserData service in the default
network <Network ID>}}

This message was sent by Atlassian JIRA

View raw message