[
https://issues.apache.org/jira/browse/CLOUDSTACK-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769371#comment-13769371
]
Nicolas FOATA commented on CLOUDSTACK-3128:
-------------------------------------------
Hi,
Indeed the LinkedHashMap solves the error into the component cloud-api
(DeployVmCmd).
But not, into the component cloud-server.
To solve completely the issue, we also have to set into
com.cloud.vm.UserVmManagerImpl.java
in the method called
protected UserVm createVirtualMachine(DataCenter zone, ServiceOffering
serviceOffering, VirtualMachineTemplate template, String hostName, String
displayName, ...)
the line
<String, NicProfile> networkNicMap = new HashMap<String, NicProfile>();
by
<String, NicProfile> networkNicMap = new LinkedHashMap<String, NicProfile>();
For closing the bug, could you set it into your patch or have I to submit diff.
Please feel free to contact me if need be,
Best regards,
> deployVm does not guearentee network interface order inside VM when called
> with ipToNetwork list parameter
> ----------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3128
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3128
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Fix For: 4.2.0
>
>
> When deployVm is called with networkIds parameter, the nics will be created
> in the Vm with the order defined by networkId parameter.
> But when ipToNetworkList parameter is passed, the order the map is presented
> in this param, is not the order the nics are created on the Vm.
--
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: http://www.atlassian.com/software/jira
