You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinav Roy (JIRA)" <ji...@apache.org> on 2013/06/04 12:30:20 UTC

[jira] [Created] (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)

Abhinav Roy created CLOUDSTACK-2840:
---------------------------------------

             Summary: [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


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 not be destroyed only after all the LB rules on this VM 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