venkata swamybabu budumuru created CLOUDSTACK-2650:
------------------------------------------------------
Summary: [Multiple IPs PerNic] disassociating public IP should
clean cloud.user_ip_address.dnat_vmip
Key: CLOUDSTACK-2650
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2650
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
Reporter: venkata swamybabu budumuru
Assignee: Jayapal Reddy
Priority: Minor
Fix For: 4.2.0
Steps to reproduce :
1. Have at least one CloudStack with advanced zone using KVM cluster
2. Have at least one non-ROOT domain user
3. deploy a VM using an isolated network.
4. Acquire a public ip and enable static nat to secondary ip
5. disassociated public ip
Observations:
- Disassociate public ip went fine but, it didnt clean dnat_vmip from the
cloud.user_ip_address table.
Here is the snippet of DB table.
mysql> select * from user_ip_address where public_ip_address like '%44.84%'\G
*************************** 1. row ***************************
id: 25
uuid: 1969d567-20d6-4dd8-b879-5a81291463a6
account_id: NULL
domain_id: NULL
public_ip_address: 10.147.44.84
data_center_id: 3
source_nat: 0
allocated: NULL
vlan_db_id: 3
one_to_one_nat: 0
vm_id: NULL
state: Free
mac_address: 15
source_network_id: 210
network_id: NULL
physical_network_id: 202
is_system: 0
vpc_id: NULL
dnat_vmip: 10.0.16.2
--
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
