You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Toshiaki Hatano (JIRA)" <ji...@apache.org> on 2013/07/15 18:48:50 UTC

[jira] [Resolved] (CLOUDSTACK-3431) KVM: cloudstack-plugin-hypervisor-kvm with BridgeVifDriver doesn't cleanup vNet due to multiple reasons

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

Toshiaki Hatano resolved CLOUDSTACK-3431.
-----------------------------------------

    Resolution: Fixed
    
> KVM: cloudstack-plugin-hypervisor-kvm with BridgeVifDriver doesn't cleanup vNet due to multiple reasons
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3431
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3431
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller, KVM
>    Affects Versions: 4.1.0, 4.1.1, 4.2.0
>         Environment: KVM hyper visor with BridgeVifDriver
>            Reporter: Toshiaki Hatano
>            Assignee: Toshiaki Hatano
>             Fix For: 4.2.0
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> When last VM which uses the guest network disappeared on the host, 
> KVM agent should clean up it's guest network bridge and vlanIf but it doesn't.
> Biggest cause is missing parameter on calling modifyvlan.sh.
> But I found there're more errors related to this issue.
> I found at least 3.
> 1) missing parameter on calling modifyvlan.sh in com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupVnet(Connect, String)
> 2) VirtualMachineName.getVnet(String) will never return vnet
> 3) com.cloud.agent.api.StopCommand.getVnet(String) will never return vnet

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