Problem: Floating IPs not automatically freed up after instance deletion
Problem/Opportunity Statement
It seems that floating IPs are not being freed up when an instance is deleted. I first suspected this because a class running on Jetstream reported running out of Public IPs. When I checked, there were about 30 unassigned IPs belonging to this project.
To reproduce, I launched 10 VMs on TRA160003 and took note of all the public IPs assigned to these instances. I waited for them to boot, then deleted them via the instance list page, ensuring the checkbox to 'Keep the public IP address' was NOT checked. After waiting a couple minutes for the instances to all delete, I checked the Public IP cards page. All 10 IPs belong to instances that were just deleted were left unassigned but still belonging to the project.
If left unchecked, over time this can consume floating IPs rather quickly. This may be related to a recent issue we had on Jetstream2 where we ran out of floating IPs.
What would success / a fix look like?
Ideally, the floating IP will be released/deleted upon instance deletion when the checkbox to keep the IP is not checked.