Bug 1293683

Summary: ceilometer floating ip pollster is broken
Product: Red Hat OpenStack Reporter: David Hill <dhill>
Component: openstack-ceilometerAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.0 (Juno)CC: dhill, dmaley, eglynn, fwissing, jruzicka, pkilambi, yeylon
Target Milestone: asyncKeywords: GSSTriaged, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-ceilometer-2014.2.3-7.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1309770 1335768 (view as bug list) Environment:
Last Closed: 2016-02-11 15:03:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1335768    
Attachments:
Description Flags
Proposed patch (from customer)
none
ceilometer.zip none

Description David Hill 2015-12-22 16:50:23 UTC 
Description of problem:
This problem looks like "nova floating-ip-list" doesn't work with another user that is not admin even though the "ceilometer" resource user has "admin" role since the ceilometer pollster make uses of novaclient v1_1, this wont work either.   The python-novaclient supports all_tenants but I've tried finding that in the nova-api and it doesn't seem to be present.  This looks similar to the following community bug:  https://bugs.launchpad.net/nova/+bug/1402514 .  Shouldn't we use neutronclient instead of novaclient?

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. floating ip pollster isn't working
2.
3.

Actual results:
floating ip pollster isn't working


Expected results:
It should be working

Additional info:
nova floating-ip-list only works for the current tenant
neutron floatingip-list seems to return a list of IPs for all tenants, shouldn't we use python-neutronclient instead of python-novaclient?
Comment 8 Freddy Wissing 2016-01-15 17:28:33 UTC 
Created attachment 1115204 [details]
Proposed patch (from customer)

Proposed patch from customer to allow ceilometer to read from neutron assigned floating ip's.
Comment 10 Dave Maley 2016-01-18 20:51:29 UTC 
Created attachment 1115963 [details]
ceilometer.zip
Comment 24 Yurii Prokulevych 2016-02-08 14:58:27 UTC 
Verified in ceilometer*-2014.2.3-7.el7ost.noarch

3 tenants with one floating ip in each.
Respective samples for each meter collected:
ceilometer sample-list -m ip.floating -l 9
+--------------------------------------+-------------+-------+--------+------+----------------------------+
| Resource ID                          | Name        | Type  | Volume | Unit | Timestamp                  |
+--------------------------------------+-------------+-------+--------+------+----------------------------+
| b35f2ea4-a029-4e2e-a1d4-9b6b2a219fc4 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:56:33.079000 |
| bbe806fb-9e12-4950-a0c7-286dbe4b0e75 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:56:33.079000 |
| 95707bbd-d11d-4c75-9d86-c9567be60d81 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:56:33.078000 |
| 95707bbd-d11d-4c75-9d86-c9567be60d81 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:55:33.002000 |
| b35f2ea4-a029-4e2e-a1d4-9b6b2a219fc4 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:55:33.002000 |
| bbe806fb-9e12-4950-a0c7-286dbe4b0e75 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:55:33.002000 |
| b35f2ea4-a029-4e2e-a1d4-9b6b2a219fc4 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:54:32.999000 |
| bbe806fb-9e12-4950-a0c7-286dbe4b0e75 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:54:32.999000 |
| 95707bbd-d11d-4c75-9d86-c9567be60d81 | ip.floating | gauge | 1.0    | ip   | 2016-02-08T14:54:32.998000 |
+--------------------------------------+-------------+-------+--------+------+----------------------------+
Comment 28 errata-xmlrpc 2016-02-11 15:03:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0170.html