[
https://issues.apache.org/jira/browse/CLOUDSTACK-9591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965366#comment-15965366
]
ASF subversion and git services commented on CLOUDSTACK-9591:
-------------------------------------------------------------
Commit 92fd5bee3d827d6811d077098d30c52f1d625ab0 in cloudstack's branch
refs/heads/4.9 from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=92fd5be ]
CLOUDSTACK-9591: Fix systemvmtemplate to not include network details
This removes nic/network specific details while exporting the systemvmtemplate
for vmware (ova file). Having this causes the ssvms to not deploy in
dvswitch-based vmware environments that have no vswitch portgroups (dummy etc).
Tested this on a local Trillian env.
Signed-off-by: Rohit Yadav <[email protected]>
> VMware dvSwitch Requires a Dummy, Standard vSwitch
> --------------------------------------------------
>
> Key: CLOUDSTACK-9591
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9591
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.6.2, 4.7.0, 4.7.1, 4.8.0, 4.9.0
> Reporter: John Burwell
> Priority: Minor
>
> When using the VMware dvSwitch, templates fail to register and VMs with the
> following secondary storage error:
> createImportSpec error: Host did not have any virtual network defined.
> Defining dummy, standard vSwitch on the same network works around this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
