[jira] [Commented] (CLOUDSTACK-2840) [N-tier : Internal LB between VPC tiers] InternalLbVm gets deleted as soon as any load balancing rule on its IP is deleted (If there are multiple LB rules on that IP , InternalLbVm gets deleted as soon as any one of those LB rules is deleted)

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 90df4e4df0ccece0693cc862c2f59214f99518cf in branch refs/heads/master from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=90df4e4 ]

CLOUDSTACK-2840: get the latest information from the DB about the number of rules in non-revoked state for the ip address when figuring out if the internal lb vm needs to be destroyed. Instead of relying on the information passed down by the NetworkManager as the network manager might pass only rules in transition state omitting the Active rules

                
> [N-tier : Internal LB between VPC tiers] InternalLbVm gets deleted as soon as any load balancing rule on its IP is deleted (If there are multiple LB rules on that IP , InternalLbVm gets deleted as soon as any one of those LB rules is deleted)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2840
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2840
>             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: Abhinav Roy
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: management-server.log
>
>
> Steps :
> ===============================
> 1. Create VPC.
> 2. Create a tier inside VPC using an internalLB network offering.
> 3. Deploy VMs in that tier .
> 4. Create a LB rule LB1 (internal LB rule) and assign vms to it.
> 5. Now create 2 more LB rules LB2 and LB3 using the source IP address same as LB1 and assign vms to LB2/LB3.
> 6. Delete LB1 or LB2 or LB3
> Expected behaviour :
> ===============================
> As soon as VMs are assigned to LB1 , InternalLbVM is created and this VM should be destroyed only after all the LB rules on this VM (or its source IP) are deleted.
> Observed behaviour :
> ===============================
> As soon as any one of the LB rules based on InternalLbVm is deleted the VM gets destroyed.

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