[Rdo-list] Possible bug? Horizon/Floating IPs

Fox, Kevin M Kevin.Fox at pnnl.gov
Mon Nov 23 23:59:28 UTC 2015

Autorelease is kind of dangerous. There is no way to get an ip back, and it may be associated in dns and you may give it back to the pool before unregistering. I always have disabled it on all my clouds to fail safe for the users.


From: rdo-list-bounces at redhat.com on behalf of Erich Weiler
Sent: Monday, November 23, 2015 2:56:07 PM
To: rdo-list at redhat.com
Subject: [Rdo-list] Possible bug? Horizon/Floating IPs

Just thought I'd throw this out there as a possible bug...  I'm running
RHEL 7.1 and OpenStack Kilo RDO.

It seems that when I terminate an instance through Horizon that has an
associated floating IP, the floating IP is *not* disassociated upon the
instance's termination.  I have to manually disassociate the floating ip
after I terminate the instance through Horizon via:

neutron floatingip-disassociate e28051c5-7fb1-4887-ade9-f1b062523ad7

for example.  Then it frees up.  Back when I was playing with the
Icehouse release of RDO OpenStack, the floating IPs were released
automatically when I terminated an instance through Horizon, so I was
surprised when I did not see the same behaviour here.

[root at os-con-01 ~]# rpm -q python-django-horizon

Just a heads up...


Rdo-list mailing list
Rdo-list at redhat.com

To unsubscribe: rdo-list-unsubscribe at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rdo-list/attachments/20151123/a8d02e71/attachment.htm>

More information about the rdo-list mailing list