cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8091) Stale entry exists for a VM NIC even after an exception while adding a new nic to vm
Date Fri, 06 Feb 2015 11:26:34 GMT

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

ASF subversion and git services commented on CLOUDSTACK-8091:
-------------------------------------------------------------

Commit 54d08a8e293e3747903250e872ec74614ff63ccf in cloudstack's branch refs/heads/4.5 from
[~saksham]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=54d08a8 ]

CLOUDSTACK-8091: Stale entry exists for a VM NIC even after an exception while adding a new
nic to vm

(cherry picked from commit 4821bfffe2813ffb43761246e75cc7cf73291d27)
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


> 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)

Mime
View raw message