flaviamissi at gmail
May 22, 2012, 4:46 PM
Post #3 of 3
(107 views)
Permalink
|
They've already fixed that in trunk:
https://bugs.launchpad.net/nova/+bug/939122
[]'s
On Tue, May 22, 2012 at 6:21 PM, Boris-Michel Deschenes <
boris-michel.deschenes [at] ubisoft> wrote:
> OK’ I’ve found this here which seems to be related (for those who
> experience the same problem):****
>
> ** **
>
> https://bugs.launchpad.net/nova/+bug/967166****
>
> ** **
>
> *De :* openstack-bounces+boris-michel.deschenes=
> ubisoft.com [at] lists [mailto:
> openstack-bounces+boris-michel.deschenes=ubisoft.com [at] lists]
> *De la part de* Boris-Michel Deschenes
> *Envoyé :* 22 mai 2012 17:09
> *À :* openstack [at] lists
> *Objet :* [Openstack] auto_assign_floating_ip in essex****
>
> ** **
>
> Hi everybody,****
>
> ** **
>
> I’ve noticed that the behavior changed in essex regarding automatic
> assignation of floating ips :****
>
> ** **
>
> **· **In Diablo, as soon as the instance was spawned, the
> floating ip was showing in nova and horizon.****
>
> **· **In Essex, the instance first spawns and then, later, as
> much as 60 seconds later the floating IP gets attached.****
>
> ** **
>
> This is not so bad but sometimes, the floating IP never appears, neither
> in horizon nor “nova list”. ****
>
> The strange thing is that the IP is there, attached to the interface of
> the nova-network server and usable, but since it does not appear in nova or
> horizon, the user will never get to know it.****
>
> ** **
>
> anyone else noticed this problem?****
>
> ** **
>
> I had this problem with AND without multi_host.****
>
> ** **
>
> Boris****
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
--
Flavia
|
