cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-4284) Add test for EIP category : enable/disable staticNAT on destroyed VM
Date Tue, 13 Aug 2013 07:14:47 GMT
venkata swamybabu budumuru created CLOUDSTACK-4284:

             Summary: Add test for EIP category : enable/disable staticNAT on destroyed VM
                 Key: CLOUDSTACK-4284
             Project: CloudStack
          Issue Type: Test
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Controller
    Affects Versions: 4.2.0
         Environment: commit id # e6d03f2322822aee331a1a2aa60190c4c755c402
            Reporter: venkata swamybabu budumuru
             Fix For: 4.2.0

Steps to be added for the test :

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 


(i) The above action will associate an EIP with is_system=1

(3) Acquire an additional public ip and enable static NAT on this.


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

As of now the 5th step is failing. This bug is being tracked under

This is test is good candidate for automation.

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