[
https://issues.apache.org/jira/browse/CLOUDSTACK-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajani Karuturi updated CLOUDSTACK-8290:
----------------------------------------
Fix Version/s: (was: Future)
4.6.0
> Add BVT to validate product bug CS-27153
> ----------------------------------------
>
> Key: CLOUDSTACK-8290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8290
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Affects Versions: Future
> Reporter: Gaurav Aradhye
> Labels: automation
> Fix For: 4.6.0
>
>
> The bug that was found is "Public IP data remained on router even after
> disabling the static NAT rule configured on public IP"
> Steps that should be added to verify absence of the defect.
> 1. Create a VM in an isolated network
> 2. Acquire a public IP in the network
> 3. Enable static NAT rule / LB rule / NAT rule for the IP
> 4. Check we are able to SSH to VM
> 5. Check the "ip addr" command output on VR, the rules should be present on
> VR for the public IP
> 6. Disable static NAT / Delete NAT/ LB Rule or disassociate public IP
> 7. Check SSH to VM, it should fail
> 8. Check the "ip addr" command output on VR, the rules should now not be
> present on VR for the public IP
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
