cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3015) VPC virtual router lists deleted nics
Date Tue, 18 Jun 2013 22:33:20 GMT


Alena Prokharchyk commented on CLOUDSTACK-3015:

Network GC thread shuts down the network if it doesn't have running user vms for some time
(network gc thread is controlled by network.gc.wait and network.gc.interval global configs).
As a result of network shutdown, the nic associated with the guest network, is being unplugged
from the VR (and corresponding nic is being removed). So this is by design.

So the bug here is - the removed nics should't be returned as a part of listRouters call as
well as those nics should never be considered for cleanup once they are removed.

> VPC virtual router lists deleted nics
> -------------------------------------
>                 Key: CLOUDSTACK-3015
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: Marcus Sorensen
>            Priority: Blocker
>              Labels: integration-test
>             Fix For: 4.1.1, 4.2.0
> Create a VPC
> Create a network in VPC
> Create a VM in network in VPC
> Shut down VM
> Wait awhile
> Observed: Something cleans up the unused network in the VPC, removing the guest network
nic from the VPC router.
> Start VM
> Observed: New nic is allocated for VPC router
> List routers
> Observed: Router shows both old and new nics.
> We need to either avoid cleaning up these nics when the aren't used, or avoid showing
them whenever a VPC/router is queried for nics.
> As a bonus, I've occasionally seen vpcs fail to be deletable. It seemed to be because
some of its nics had no broadcast URI (the removed ones), and a NULL pointer was thrown.

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:

View raw message