[ceilometer]ceilometer statistics list command fail

[Artem Minasyan]

After deploy environment we execute command ceilometer statistics -m cpu with the following error:
Invalid input for field/attribute min. Value: '29200000000'. Wrong type. Expected '<type 'float'>', got '<class 'bson.int64.Int64'>' (HTTP 400) (Request-ID: req-9f69697f-209e-4f23-8fd0-6331178364f7)

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "521"
  build_id: "521"
  fuel-nailgun_sha: "bae6d0062e0825d81409a04bcb4979302f8c65ea"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "658be72c4b42d3e1436b86ac4567ab914bfb451b"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "29829b131ca802830bc5a9a131c83cd0f43f702b"
  fuel-ostf_sha: "7bcddf18020f2d94a553a441ff57dff9632865df"
  fuel-mirror_sha: "c25d8931e30322ecf43246c8a957e376259b685c"
  fuelmenu_sha: "e071216cb214e34b4d861478033425ee6a54a3be"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "a365f05b903368225da3fea9aa42afc1d50dc9b4"

[Nadya Privalova (nprivalova)]

https://review.openstack.org/#/c/287993/ in upstream should fix that.

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Nadya Privalova (nprivalova)]

Fixed in upstream

[Artem Minasyan (aminasyan)]

Verified on ISO: http://paste.openstack.org/show/510473/

[Adam Heczko (aheczko-mirantis)]

This affects also MOS 8.0 and fix is present in upstream Liberty.

[Denis Meltsaykin (dmeltsaykin)]

Adam, first of all, please don't set "mu-X" milestones on your own:
1) this makes no effect on our plans
2) it makes mistaken belief that the bug will be fixed in that milestone

The second one - 8.0 is being synchronized with Liberty on a regular basis, you don't need to reopen a bug if its fix is present in stable/liberty.