cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4630) Cannot apply userdata unless all NICs support userdata
Date Tue, 17 Sep 2013 23:17:52 GMT


Alena Prokharchyk commented on CLOUDSTACK-4630:

Agree with you, Dave, my last comments shouldn't purely relies on the fact that only VR supports
User Data at the moment. It should be more generic (just the way our other services behave),
and work like this:

* when userData is passed to the client API, check if at least one VM's nic (network) supports
it. If not, fail the API.
* After the command is down to the network manager, pass it to the network element only when
the element supports the service. And let the element decide whether it needs to be applied
for the nic - for example, VR would still do it for default network only.

> Cannot apply userdata unless all NICs support userdata
> ------------------------------------------------------
>                 Key: CLOUDSTACK-4630
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.1
>         Environment: CentOS 6.4 x86_64
>            Reporter: Dave Garbus
>            Assignee: Alena Prokharchyk
>              Labels: integration-test
>             Fix For: Future
> To reproduce this issue, follow the steps below:
> 1. Create two network offerings, one with UserData service (virtual router) and one without.
> 2. Add two NICs to the virtual machine with networks corresponding to each network offering
> 3. Call updateVirtualMachine on the VM, specifying userdata.
> The update will fail with the following error:
> : Service UserData is not supported in the network id=217
> If the NIC without UserData support is removed, the update will go through without issue.
In my opinion, this should not cause the whole update to fail, but only update UserData for
the relevant NICs.
> Full trace below:
> 2013-09-09 14:40:21,316 ERROR [cloud.api.ApiServer] (http-6443-exec-3:null) unhandled
exception executing api command: updateVirtualMachine
> Service UserData is not supported in
the network id=217
>         at
>         at$InterceptorDispatcher.intercept(
>         at
>         at
>         at
>         at$InterceptorDispatcher.intercept(
>         at org.apache.cloudstack.api.command.user.vm.UpdateVMCmd.execute(
>         at
>         at
>         at
>         at
>         at
>         at javax.servlet.http.HttpServlet.service(
>         at javax.servlet.http.HttpServlet.service(
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(
>         at org.apache.catalina.core.StandardWrapperValve.invoke(
>         at org.apache.catalina.core.StandardContextValve.invoke(
>         at org.apache.catalina.core.StandardHostValve.invoke(
>         at org.apache.catalina.valves.ErrorReportValve.invoke(
>         at org.apache.catalina.valves.AccessLogValve.invoke(
>         at org.apache.catalina.core.StandardEngineValve.invoke(
>         at org.apache.catalina.connector.CoyoteAdapter.service(
>         at org.apache.coyote.http11.Http11NioProcessor.process(
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(
>         at$
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message