I should have pointed to the gerrit that's an external tracker on that. It shows the root cause is that the disk_image_dynamic table (part of the engine) isn't getting updated. It's a view of that table that's used for the stats that you see online and is used by the collector for dwh.
http://gerrit.ovirt.org/#/c/12961/ It says core: disk_image_dynamic statistics (#892596) vdsm sends disk statistics per disk, while disk_image_dynamic table contains disk_image ids (volumes). Hence the update on disk ids that VdsUpdateRunTimeInfo generates, actually does nothing. A quick fix for this problem is that VdsUpdateRunTimeInfo now updates by the AI id, so statistics are saved. On Fri, Sep 20, 2013 at 3:02 PM, Joop <jvdw...@xs4all.nl> wrote: > John Taylor wrote: > >> Hi Joop, >> >> If you're on 3.1 or 3.2 I think this is the bug >> https://bugzilla.redhat.com/**show_bug.cgi?id=892596<https://bugzilla.redhat.com/show_bug.cgi?id=892596> >> >> -John >> >> I'm on 3.2.2 el6. Reading that BZ suggests that it is 3.2 related but > also it speaks of dhw. I don't have the reporting part of ovirt-engine > installed so don't know it that is causing the zero values. > > > Joop > > ______________________________**_________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org/mailman/listinfo/users> >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
