Marcus Sorensen created CLOUDSTACK-433:
------------------------------------------
Summary: IP addresses can be left assigned and orphaned when
static NAT assign fails
Key: CLOUDSTACK-433
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-433
Project: CloudStack
Issue Type: Bug
Components: Network Controller
Affects Versions: 4.0.0
Environment: KVM (tested with VPC router, may or may not affect normal
virtual router)
Reporter: Marcus Sorensen
If I attempt to create a static NAT and it fails, the IP address that was added
to the router to host that static NAT is left on the router. This is fine,
except I can then unassign the ip address, and cloudstack marks it as released
and can assign it to someone else, except the IP is still live on the router.
If I had to guess this is an artifact from the way VPC handles IPs, that is it
doesn't assign them to anything until it's actually used for a rule such as
static nat or port forwarding. It may affect more than just static NAT.
So when a job like creating static nat is run, it first associates the IP, then
applies the static nat, and if the latter fails then it thinks the associate IP
failed as well (or at least doesn't clean up afterward).
--
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
