Probably that LOG statement is a line added for debugging purposes.
There are several probable causes for a floating ip being down. If you see
any traceback in the neutron server or l3-agent that will probably
immediately reveal the root cause.
On the other hand, lack of any traceback might indicate communication
issues between the server and the l3 agent.
Salvatore
On 22 September 2016 at 16:53, Brian Haley <brian.ha...@hpe.com> wrote:
> On 09/22/2016 10:19 AM, Barber, Ofer wrote:
>
>> when i assign a floating IP to a server, i see that the status of the
>> floating
>> IP is "down"
>>
>> why is that so ?
>>
>> *_code:_*
>>
>> LOG.info("\n<====== float IP address: %s and status: %s ======>" %
>> (float_ip['floating_ip_address'],float_ip['status']))
>>
>> *_Output:_*
>>
>> <====== float IP address: 10.63.101.225 and status: DOWN ======>
>>
>
> I couldn't find that code anywhere, what release was this on?
>
> From a Newton-based system created yesterday, this is the message in the
> l3-agent log when I associate a floating IP:
>
> Floating ip 4c1b4571-a003-43f2-96a1-f7073cd1319d added, status ACTIVE
>
> -Brian
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
