cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murali Reddy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-2345) [GSLB] deleting GSLB rules is not cleaning server info from GSLB device
Date Mon, 29 Sep 2014 20:25:35 GMT

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

Murali Reddy updated CLOUDSTACK-2345:
-------------------------------------
    Assignee:     (was: Murali Reddy)

> [GSLB] deleting GSLB rules is not cleaning server info from GSLB device
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2345
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2345
>             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
>         Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
>            Reporter: venkata swamybabu budumuru
>            Priority: Minor
>             Fix For: Future
>
>         Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. create CloudStack setup with at least 2 zones
> 2. create a GSLBRule with at least 2 LB rules 
> 3. Delete all the above created rules and issue "show server" on GSLB device
> Observations :-
> (i) Found that server list is not cleaned up on the Netscaler devices
> Here is the snippet from Netscaler:
> > show server
> 1)      Name:      10.147.44.21      State:ENABLED 
>         IPAddress:    10.147.44.21 
> 2)      Name:      10.147.54.14      State:ENABLED 
>         IPAddress:    10.147.54.14 
> 3)      Name:   Cloud-Server--10.147.44.61      State:ENABLED 
>         IPAddress:    10.147.44.61 
> 4)      Name:   Cloud-Server--10.147.54.161      State:ENABLED 
>         IPAddress:   10.147.54.161 
>  Done
> Attaching all the required logs to the bug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message