[
https://issues.apache.org/jira/browse/CLOUDSTACK-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706605#comment-13706605
]
Prachi Damle commented on CLOUDSTACK-3191:
------------------------------------------
Few tables have been added for future refactoring work related to
cloud-engine-orchestration during javelin feature branch. This table is one of
them, data is not referred anywhere but the inflow of data to this table during
vm deployment is implemented.
Keeping this table around right now is harmless. These will either be
removed/schema modified in upcoming vm sync related feature changes.
> vm_network_map table is not updated when we call addNicToVirtualMachine and
> removeNicFromVirtualMachine
> --------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3191
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3191
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Reporter: shweta agarwal
> Assignee: Prachi Damle
> Fix For: 4.2.0
>
>
> Repro steps:
> 1. Create a VM with multiple network
> 2. Note All network related entries gets populated in vm_network_map table
> 3.Add a new network to the VM
> Bug :
> vm_network-map not updating new network added to VM
> 4. Remove network from VM
> Bug:
> vm_network_map is not updated with removed network for VM
> so in a sense we are creating inconsistency in our Database table
> vm_network_map by not adding all the networks that belong to VM and by not
> removing the network that no longer belongs to a 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
