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?
Created attachment 1115204 [details] Proposed patch (from customer) Proposed patch from customer to allow ceilometer to read from neutron assigned floating ip's.
Created attachment 1115963 [details] ceilometer.zip
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 | +--------------------------------------+-------------+-------+--------+------+----------------------------+
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