[
https://issues.apache.org/jira/browse/LIBCLOUD-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060131#comment-14060131
]
ASF subversion and git services commented on LIBCLOUD-593:
----------------------------------------------------------
Commit 784e7beb05df95fe6d85c9a0720c8234670229d4 in libcloud's branch
refs/heads/trunk from [~atsaki]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=784e7be ]
LIBCLOUD-593: CloudStack driver's create_node fails to join network_id when
network_id is int
Closes #336
Signed-off-by: Sebastien Goasguen <run...@gmail.com>
> CloudStack driver's create_node fails to join network_id when network_id is
> int
> -------------------------------------------------------------------------------
>
> Key: LIBCLOUD-593
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-593
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Affects Versions: 0.13.0, 0.13.1, 0.13.2, 0.14.0-beta3, 0.13.3
> Reporter: Atsushi Sasaki
>
> CloudStack driver's create_node accept an argument "networks" it is used to
> specify networks the node will be connected to.
> networks is a list of CloudStackNetwork instances and their id is joined to
> construct a argument for CloudStack API's deployVirtualMachine in
> create_node. It is OK when network id is string but some implementation uses
> integer network id.
> When network id is integer, the code like following fails.
> networks = driver.ex_list_networks()
> node = driver.create_node(location, image, size, networks=networks)
> This patch convert network id into str explicitly before joining network ids.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
