Warning messages for unused floating IPs

Bug #1604328 reported by Dr. Jens Harbott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Fix Released
Undecided
Pradeep Kilambi

Bug Description

When there are floating IPs in Neutron which are allocated but not assigned to an instance, one will see lots of warnings in the logs like this:

2016-07-19 06:29:00.863 5895 INFO ceilometer.agent.manager [req-d685eb26-b84d-4d6b-80a9-1b81d3cee788 admin - - - -] Polling pollster ip.floating in the context of meter_source
2016-07-19 06:29:01.334 5895 WARNING ceilometer.network.floatingip [req-d685eb26-b84d-4d6b-80a9-1b81d3cee788 admin - - - -] Invalid status, skipping IP address 1.2.3.4
2016-07-19 06:29:01.334 5895 WARNING ceilometer.network.floatingip [req-d685eb26-b84d-4d6b-80a9-1b81d3cee788 admin - - - -] Invalid status, skipping IP address 1.2.3.5
2016-07-19 06:29:01.336 5895 WARNING ceilometer.network.floatingip [req-d685eb26-b84d-4d6b-80a9-1b81d3cee788 admin - - - -] Invalid status, skipping IP address 1.2.3.6

This is fixed in master as a side effect of https://review.openstack.org/308553 but still happens in Mitaka 6.1.1.

Revision history for this message
zhangguoqing (474751729-o) wrote :

I have verified when there are floating IPs in Neutron which are allocated but not assigned to an instance, the status is 'DOWN' rather than 'None' which lead to print warning message.

[root@dev ~(keystone_admin)]# neutron floatingip-create public
Created a new floatingip:
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| description | |
| dns_domain | |
| dns_name | |
| fixed_ip_address | |
| floating_ip_address | 172.24.4.228 |
| floating_network_id | 1bd6a834-8e87-4a17-a560-c3fd84dcd2ba |
| id | 1e301a53-e0a9-4923-9c25-b2f93196c45f |
| port_id | |
| router_id | |
| status | DOWN |
| tenant_id | 7e39a8e2ec774102835ba7e31c82ad84 |
+---------------------+--------------------------------------+

Changed in ceilometer:
assignee: nobody → zhangguoqing (474751729-o)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ceilometer (master)

Fix proposed to branch: master
Review: https://review.openstack.org/344247

Changed in ceilometer:
status: New → In Progress
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

The issue doesn't exist in master for me, I already proposed a backport of the patch that seems to fix it: https://review.openstack.org/336009

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on ceilometer (master)

Change abandoned by zhangguoqing (zhang.guoqing@99cloud.net) on branch: master
Review: https://review.openstack.org/344247
Reason: https://review.openstack.org/#/c/336009/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ceilometer (stable/mitaka)

Reviewed: https://review.openstack.org/336009
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=0e0fe559b9f365a78504bf2742dab995f62030ce
Submitter: Jenkins
Branch: stable/mitaka

commit 0e0fe559b9f365a78504bf2742dab995f62030ce
Author: Pradeep Kilambi <email address hidden>
Date: Wed Apr 20 15:48:38 2016 -0400

    Refactor floatingip pollster to use discovery

    Note: The bug isn't present in master because it is fixed as a side
    effect of the patch that is cherry-picked here. Still it seems better to
    use this code than to come up with a dedicated bug-fix patch.

    Closes-Bug: 1604328

    Change-Id: I47cd14fb6c06ea2c83adab987a0442ef9bd3f404
    (cherry picked from commit c262389819cc31c9b87ca5207a809fb2aa1ac882)

tags: added: in-stable-mitaka
gordon chung (chungg)
Changed in ceilometer:
status: In Progress → Fix Released
assignee: zhangguoqing (474751729-o) → Pradeep Kilambi (pkilambi)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ceilometer 6.1.4

This issue was fixed in the openstack/ceilometer 6.1.4 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.