4:56 p.m.
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@os-con-01 ~]# rpm -q python-django-horizon
python-django-horizon-2015.1.0-5.el7.noarch
Just a heads up...
cheers,
erich
5:59 p.m.
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.
Kevin
________________________________
From: rdo-list-bounces(a)redhat.com on behalf of Erich Weiler
Sent: Monday, November 23, 2015 2:56:07 PM
To: rdo-list(a)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@os-con-01 ~]# rpm -q python-django-horizon
python-django-horizon-2015.1.0-5.el7.noarch
Just a heads up...
cheers,
erich
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
6:10 p.m.
Hi Kevin,
Thanks for the reply! I think we may be talking about two different
things however... I'm not looking to release the IP back to the public
pool, I'm just looking to disassociate from a deleted VM when the
instance is terminated. After I terminate the instance, it still shows
as stuck to the deleted instance, which is kind of pointless.
After I disassociate the floating IP via 'neutron
floatingip-disassociate', it releases the IP back to my own allocated IP
list, so I most definitely can re-use that IP for another instance
easily. I agree that if I unallocated it with 'neutron
floatingip-delete', then I may not get it back, but with 'neutron
floatingip-disassociate' I still own it as a user of a project.
Just checking if the decision was made to stop dissociating the floating
IPs upon instance termination after Icehouse, or if it was overlooked in
Kilo?
Thanks for the reply!
cheers,
erich
On 11/23/2015 03:59 PM, Fox, Kevin M wrote:
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.
Kevin *
*
------------------------------------------------------------------------
*From:* rdo-list-bounces(a)redhat.com on behalf of Erich Weiler
*Sent:* Monday, November 23, 2015 2:56:07 PM
*To:* rdo-list(a)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@os-con-01 ~]# rpm -q python-django-horizon
python-django-horizon-2015.1.0-5.el7.noarch
Just a heads up...
cheers,
erich
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
6:21 p.m.
There is a config value in horizon to autorelease floating ips. Ive never seen nova not
autodissassociate on delete. That may be a misconfiguration between nova and neutron? I
dont think horizon is involved in that path. Maybe try from the cli to double check?
Thanks,
Kevin
________________________________
From: Erich Weiler
Sent: Monday, November 23, 2015 4:10:45 PM
To: Fox, Kevin M; rdo-list(a)redhat.com
Subject: Re: [Rdo-list] Possible bug? Horizon/Floating IPs
Hi Kevin,
Thanks for the reply! I think we may be talking about two different
things however... I'm not looking to release the IP back to the public
pool, I'm just looking to disassociate from a deleted VM when the
instance is terminated. After I terminate the instance, it still shows
as stuck to the deleted instance, which is kind of pointless.
After I disassociate the floating IP via 'neutron
floatingip-disassociate', it releases the IP back to my own allocated IP
list, so I most definitely can re-use that IP for another instance
easily. I agree that if I unallocated it with 'neutron
floatingip-delete', then I may not get it back, but with 'neutron
floatingip-disassociate' I still own it as a user of a project.
Just checking if the decision was made to stop dissociating the floating
IPs upon instance termination after Icehouse, or if it was overlooked in
Kilo?
Thanks for the reply!
cheers,
erich
On 11/23/2015 03:59 PM, Fox, Kevin M wrote:
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.
Kevin *
*
------------------------------------------------------------------------
*From:* rdo-list-bounces(a)redhat.com on behalf of Erich Weiler
*Sent:* Monday, November 23, 2015 2:56:07 PM
*To:* rdo-list(a)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@os-con-01 ~]# rpm -q python-django-horizon
python-django-horizon-2015.1.0-5.el7.noarch
Just a heads up...
cheers,
erich
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
6:31 p.m.
Hmmm.. When I delete an instance from the command line via:
nova delete 33190d5c-da79-41f7-bc55-899f8f15cb7c
It deletes the instance, but the floating IP remains stuck to that
deleted instance even after it's deleted. I guess it has nothing to do
with horizon....
I wonder where I misconfigured it...
On 11/23/2015 04:21 PM, Fox, Kevin M wrote:
There is a config value in horizon to autorelease floating ips. Ive
never seen nova not autodissassociate on delete. That may be a
misconfiguration between nova and neutron? I dont think horizon is
involved in that path. Maybe try from the cli to double check?
Thanks,
Kevin *
*
------------------------------------------------------------------------
*From:* Erich Weiler
*Sent:* Monday, November 23, 2015 4:10:45 PM
*To:* Fox, Kevin M; rdo-list(a)redhat.com
*Subject:* Re: [Rdo-list] Possible bug? Horizon/Floating IPs
Hi Kevin,
Thanks for the reply! I think we may be talking about two different
things however... I'm not looking to release the IP back to the public
pool, I'm just looking to disassociate from a deleted VM when the
instance is terminated. After I terminate the instance, it still shows
as stuck to the deleted instance, which is kind of pointless.
After I disassociate the floating IP via 'neutron
floatingip-disassociate', it releases the IP back to my own allocated IP
list, so I most definitely can re-use that IP for another instance
easily. I agree that if I unallocated it with 'neutron
floatingip-delete', then I may not get it back, but with 'neutron
floatingip-disassociate' I still own it as a user of a project.
Just checking if the decision was made to stop dissociating the floating
IPs upon instance termination after Icehouse, or if it was overlooked in
Kilo?
Thanks for the reply!
cheers,
erich
On 11/23/2015 03:59 PM, Fox, Kevin M wrote:
> 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.
>
> Kevin *
> *
> ------------------------------------------------------------------------
> *From:* rdo-list-bounces(a)redhat.com on behalf of Erich Weiler
> *Sent:* Monday, November 23, 2015 2:56:07 PM
> *To:* rdo-list(a)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@os-con-01 ~]# rpm -q python-django-horizon
> python-django-horizon-2015.1.0-5.el7.noarch
>
> Just a heads up...
>
> cheers,
> erich
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
>https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
9:11 a.m.
On 24/11/15 01:31, Erich Weiler wrote:
Hmmm.. When I delete an instance from the command line via:
nova delete 33190d5c-da79-41f7-bc55-899f8f15cb7c
It deletes the instance, but the floating IP remains stuck to that
deleted instance even after it's deleted. I guess it has nothing to do
with horizon....
I wonder where I misconfigured it...
My reasoning here and with my horizon upstream hat on:
I see horizon as alternate input method to cli. Thus horizon should not
implement additional functionality here for basic tasks.
Matthias
9:39 a.m.
Hi,
We had a 'similar' persistent floating ip issue a while ago that was
reported to RH and fixed. All caused by HA routers.
https://bugs.launchpad.net/neutron/+bug/1505700
https://review.openstack.org/#/c/234247/
Summary -
Created a new user/project/router.
Created an instance with a floating ip.
The floating ip correctly appeared on the qrouter and the instance was
accessible via ssh externally.
We disassociated the floating ip from the instance BUT the floating ip
was still bound to the qrouter.
We released the floating ip BUT the floating ip was still bound to the
qrouter.
We logged into Horizon as a different user/project (different qrouter).
We managed to allocate the floating ip still bound to the other qrouter
to this qrouter. This ip was then associated to an instance. So the
same floating ip was bound to two different qrouters and effectively
associated to two different instances in two separate projects.
When you ssh to the floating ip you connected to either instance
depending on the ARP cache.
Charles
On 23/11/2015 22:56, Erich Weiler wrote:
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@os-con-01 ~]# rpm -q python-django-horizon
python-django-horizon-2015.1.0-5.el7.noarch
Just a heads up...
cheers,
erich
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
--
Charles Short
Cloud Engineer
Virtualization and Cloud Team
European Bioinformatics Institute (EMBL-EBI)
Tel: +44 (0)1223 494205
3082
days inactive
3083
days old
6 comments
4 participants
participants (4)
-
Charles Short -
Erich Weiler -
Fox, Kevin M -
Matthias Runge