Import Unmanaged VM fails due to no matching network found (vCenter) #10211
Replies: 5 comments 1 reply
|
Thanks for opening your first issue here! Be sure to follow the issue template! |
0 replies
|
@ttmader I'm not sure but ACS UI might not be finding a matching network as the NIC for the VM returns a VLAN ID 0. Is it possible for you to test an import of a VM having a NIC with a different VLAN? |
0 replies
|
I'm not able to reproduce this with 4.19 pacakges |
0 replies
|
@ttmader , have you tried 4.19? Is this still an issue for you? |
1 reply
|
closed this for lack of interaction, please reopen or open a new item if applicable |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
I have a virtual switch configured in vCenter Switch0, associated with a physical nic. A port group has been created for virtual machines called LAN:
In cloudstack, when trying to import a VM, it appears as lan id 0, and it has been created with that id:
I'm sure I'm doing something wrong, that's why I'm asking for help.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
All reactions