Page MenuHomePhabricator

Hostnames assigned to floating IP persist when deallocated
Closed, ResolvedPublic

Description

When allocating a "new" IP from the pool, any hostname formerly associated to it remains attached.

Releasing an IP back to the pool should remove any hostnames.


Version: unspecified
Severity: minor

Details

Reference
bz53816

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 1:54 AM
bzimport set Reference to bz53816.

Doesn't the web interface prevent release of an IP if it has hostnames?

I'm uncertain; I ran into this I think after a deleted /project/ ended up with IPs back in the pool.

Andrew set Security to None.
Andrew subscribed.

Ping... Another case of that bug has been found by @chasemp.

AlexMonk-WMF subscribed.

Nope, those are fixed IPs.

I think what this bug intends is: Say you have a project with an instance, and a floating IP assigned to that instance. You create $somename.$project.wmflabs.org IN A $floatingip. But you then delete the floating IP - leaving the record useless. I'm not sure if we should rely on projectadmins clearing this up or not.

Maybe Horizon should detect this and give a warning, but that'd be an upstream thing.

Bstorm claimed this task.
Bstorm subscribed.

This should be resolved after version upgrades of Openstack. If this isn't true, please re-open.