[jira] [Resolved] (CLOUDSTACK-8091) Stale entry exists for a VM NIC even after an exception while adding a new nic to vm

["Saksham Srivastava (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saksham Srivastava resolved CLOUDSTACK-8091.
--------------------------------------------
    Resolution: Fixed

> Stale entry exists for a VM NIC even after an exception while adding a new nic to vm
> ------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8091
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8091
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.5.0
>            Reporter: Saksham Srivastava
>            Assignee: Saksham Srivastava
>
> Steps:
> ================================================
> 1. Create an Isolated Network.
> 2. Make sure there are no guest vlans remaining.
> 3. Add an additional NIC to the VM with the network created in step 1.
> Observations:
> =================================================
> 1. Adding network to the VM throws an error message
> And on refreshing the page, the new NIC shows up on CloudStack and acquires an IP address. This is due to the stale entry present in the database.
> 2. On the Hypervisor side, the NIC isn't mapped to the VM. Its only on the CloudStack side that we have the entry.
> Expected:
> =================================================
> Need to clear the stale entry if the add NIC did not go through with success.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)