You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/07/02 00:31:21 UTC

[jira] [Commented] (CLOUDSTACK-3191) vm_network_map table is not updated when we call addNicToVirtualMachine and removeNicFromVirtualMachine

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697275#comment-13697275 ] 

Alena Prokharchyk commented on CLOUDSTACK-3191:
-----------------------------------------------

Checked with Prachi - the person who added this table originally. She said that as the code never reads from this table, so its ok for it not to be updated. Prachi, if the table is no longer in use, may be it would make sense to remove it?
                
> 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
>             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