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/04/02 14:11:15 UTC

[jira] [Created] (CLOUDSTACK-1891) [AWS style Health Checks]After upgrade from 4.0 to 4.2 , cleanup not happening properly after releasing the IP on which LB was configured

Abhinav Roy created CLOUDSTACK-1891:
---------------------------------------

             Summary: [AWS style Health Checks]After upgrade from 4.0 to 4.2 , cleanup not happening properly after releasing the IP on which LB was configured
                 Key: CLOUDSTACK-1891
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1891
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.0
            Reporter: Abhinav Roy
            Assignee: Rajesh Battala
             Fix For: 4.2.0


Steps :
==============================
1. Upgrade MS from 4.0 to 4.2
2. Go to the existing Netscaler network, acquire IP and create a LB rule.
3. configure health checks on the LB rule.
4. Release the IP acquired in step 2


Expected behaviour :
=============================
IP should be relased, LB rule and the LB monitor created on NS device also should be deleted.


Observed behaviour :
============================
IP is released
LB rule doesn't get deleted on CS but the corresponding lb vserver is deleted from NS
LB health check policy gets deleted on CS but the corresponding monitor doesn't get deleted from NS



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