Description of problem: Cloudforms is using UTC in calculating chargeback eventhough a local timezone was already set in the Reports Chargeback Interval. Here's a sample screenshot taken @July 16 9:36 am Sydney Time(July 15 11:36pm UTC) sample_chargeback_report.png Sample chargeback report generated @July 16 9:36am EST for an hourly reporting range from yesterday to today-partial but only shows the previous day report_hourly_timezone.png (Report's chargeback interval settings) Version-Release number of selected component (if applicable): cfme 5.3 How reproducible: always Steps to Reproduce: 1. Create chargeback rates and attach to a provider/vms 2. Create a chargeback report, in filtering section use local TimeZone as Chargeback Interval 3. queue report Actual results: chargeback report use UTC timezone as interval Expected results: should use local timezone interval Additional info:
Nandini, can you please try to retest this, thanks!
Nandini did you get chance to reproduce this, Let me know if you need any additional information on this.
I could reproduce the issue on a 5.3 appliance.I haven't had a chance to reproduce it on a 5.4 appliance. Reproducer steps: 1)I set the appliance Time Zone to non-UTC(Australian Eastern Time) 2)Created a Time Profile for Australian Eastern Time. 3)In chargeback interval,I selected the following options: Daily ending with - Today(Partial) Going back - 1 day 4)I then generated a chargeback report at 4:08 Australian Eastern Time on 8/4/15,which is 18:08 UTC on 8/3/15.The report doesn't contain data for 8/4/15.
Yes, I have looked into it and discovered that the bug is actually in the chargeback report editor. When a user selects a time zone on the filter tab and clicks the save button the selected time zone was never saved in the report. I verified that once a time zone (other than UTC, which is the default) is saved in the report it is honored when the report is generated. I've created a PR for this - https://github.com/ManageIQ/manageiq/pull/3909
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/9ab16c4c7d4c7a3bd9ba1b98a10b6f16b047ed5e commit 9ab16c4c7d4c7a3bd9ba1b98a10b6f16b047ed5e Author: Gregg Tanzillo <gtanzill> AuthorDate: Mon Aug 17 17:58:26 2015 -0400 Commit: Gregg Tanzillo <gtanzill> CommitDate: Mon Aug 17 17:58:26 2015 -0400 Fixed bug where time zone selected in report editor was not getting saved with report. https://bugzilla.redhat.com/show_bug.cgi?id=1243695 app/controllers/report_controller/reports/editor.rb | 1 + 1 file changed, 1 insertion(+)
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/4775b1030b0b52caee3c41b22b630b8d9838f316 commit 4775b1030b0b52caee3c41b22b630b8d9838f316 Author: Gregg Tanzillo <gtanzill> AuthorDate: Mon Aug 17 23:42:36 2015 -0400 Commit: Gregg Tanzillo <gtanzill> CommitDate: Mon Aug 17 23:42:36 2015 -0400 Added test. https://bugzilla.redhat.com/show_bug.cgi?id=1243695 .../miq_report_controller/reports/editor_spec.rb | 49 ++++++++++++++++++++++ 1 file changed, 49 insertions(+)
Created attachment 1067477 [details] Chargeback filter set to sydney timezone
Created attachment 1067478 [details] CFME 5.4 patched Chargeback report
Created attachment 1067479 [details] CFME 5.4 unpatched Chargeback report
Created attachment 1067480 [details] Discrepancies on the Total Cost reports between CFME 5.3 and CFME 5.4 (example Virtual Machine "acmeesg01-0", "cperez-test-recon-01", "demolin01" for the date of 8/25/2015)
Hi, any update on this one? Can we close it? As far as I can tell the provided hotfix addresses the reported issue. Thanks.
Hello, I have been looking at this in 5.5.0.11, and if I specify some timezone in the report configuration (eg. Eastern US time) and the appliance is in UTC, the times in the web report and also in the downloaded report are still shown as UTC. I did exactly what Nandini and Prasad did ... or not? Any more details?
Hi Milan, Are you referring to the chargeback report mentioned in the original bug? I don't see any columns on that report, or any chargeback report, that have a time. Only the date range column, but that does not have a time element. With that, the time zone configured in a chargeback report is only for grouping the metrics by day, week or month. It users the time zone to determine when a day, week or month starts in that time zone so that the metrics can be grouped accordingly.Hope this helps. Gregg
Yes, I can see that now. Checked in 5.5.0.13
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://access.redhat.com/errata/RHSA-2015:2551