[
https://issues.apache.org/jira/browse/CLOUDSTACK-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-3511.
-------------------------------------------
Resolution: Fixed
Assignee: Alena Prokharchyk (was: Alex Karasulu)
Already fixed by 2e2ee2f3ed389b1b1a8a89eae8a641314417ca83
> When enableStatitNat called twice for the same ip/vm combination, the second
> call unsets vm_id and one_to_one_nat flags in the DB
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3511
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3511
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Priority: Critical
> Fix For: 4.2.0
>
>
> Steps to reproduce:
> 1) Enable static nat for the ip address id=1, vm id=2. The ip address is
> marked as static nat, and updated with the vm_id. Everything is fine so far.
> 2) Execute the command from the step #1 once again, the same vm id and
> ipaddressid. The command errors out as expected "Failed to enable static nat
> for the ip address with specified ipId as vm with specified vmId is already
> associated with specified currentIpId"
> The bug is - along with throwing the exception, the code resets static_nat
> and vm_id flags to NULL in the DB, so the ip becomes non static nat enabled.
--
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
