Hide Forgot
Description of problem: After applying a bugfix from https://bugzilla.redhat.com/show_bug.cgi?id=1370422, the chargeback of openstack instance are blank. Version-Release number of selected component (if applicable): CFME-5.6.1 Steps to Reproduce: 1. Create a tag category called 'chargeback'; 2. Create two tags 'sample0' and 'sample1' in the category that we just created; 3. Switch to 'Cloud Intel' -> 'Chargeback' -> 'Rates' and create two new ones called 'Low-Rate Sample' and 'High-Rate Sample'; 4. Switch to 'Assignments', and assign rate 'Low-Rate Sample' to tag 'sample0' and 'High-Rate Sample' to 'sample1'; 5. Switch to 'Compute' -> 'Cloud' -> 'Instances', tag some vms/instances with 'sample0', and the others with 'sample1'; 6. Switch to 'Cloud Intel' -> 'Reports' -> 'Reports', Create a new report called 'Custom Chargeback', which is based on 'Chargeback for VMs'; 7. Edit the report we just created, and add the following fields to the report: * CPU Total * CPU Total Cost * Memory Total * Memory Total Cost * Storage Total * Storage Total Cost * Owner * Fixed Total Cost * Total Cost 8. Then click the 'Queue' button to generate a new report sheet. Actual results: Host/Node utilization can be seen under Cloud -> Instance Expected results: Additional info:
Reproducer: 10.65.9.185(CFME-5.6.1.2) Dumped customer's vmdb I see non-zero values for column 'cpu_usage_rate_average' for metrics and metric_rollups tables. The column 'cpu_usage_rate_average' had ZERO value. before applying the patch. --- select cpu_usage_rate_average from metric_rollups where resource_name='helloworld'; select cpu_usage_rate_average from metrics where resource_name='helloworld'; --- Let me know if you need anything else. -- Sachin
Any update on this bug?
Hello Gregg, Are you working on a reproducer(db dump attached) or do you want me to create a new one?
I cannot reproduce this one. I didn't used the db. However, I picked 5.6.4.0.20170201130751_9521533 (that has bug 1370586 included). I added fresh openstack and I followed the reproducer steps closely. The chargeback shows values just fine. Sachin, does the customer still experiences the problem?
Customer did'nt came back and the case has been archived. If the chargeback is working as expected. We can close this case.