cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <>
Subject [jira] [Closed] (CLOUDSTACK-4206) [EIP/ELB] Failed to disableStaticNAT when the userVM is in destroyed state.
Date Wed, 14 Aug 2013 09:47:47 GMT


venkata swamybabu budumuru closed CLOUDSTACK-4206.

Have verified this on the latest build and it works fine without any issues. Closing the bug.
> [EIP/ELB] Failed to disableStaticNAT when the userVM is in destroyed state.
> ---------------------------------------------------------------------------
>                 Key: CLOUDSTACK-4206
>                 URL:
>             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 id # 7fced6460f13468369550c968670c7d0b9837949
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.2.0
>         Attachments: logs.tgz
> Steps to reproduce:
> 1. Have latest CloudStack setup with at least one EIP/ELB enabled zone.
> 2. Login as non-ROOT domain user, deploy at least one VM 
> Observations:
> (i) The above action will associate an EIP with is_system=1
> (3) Acquire an additional public ip and enable static NAT on this.
> Observations:
> (ii) This will release the is_system=1 ip (The ip mentioned in observation (i)) and enables
staticNAT on the acquired ip with is_system set to 0
> (4) Destroy the userVM 
> (5) Try to disableStaticNat before the above destroyed VM moves to expunging.
> Observations:
> (iii) It fails with the following error in mgmt server logs.
> Attaching all the logs along with db dump to the bug.

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:

View raw message