Red Hat Bugzilla – Bug 1204826
Cloudforms widget not refreshed as scheduled
Last modified: 2016-07-20 17:42:43 EDT
Description of problem: Widgets are sometimes not getting refreshed when scheduled to run at 0 minute of an hour. Scheduling widgets to run 5 or 10 minutes after the hour fixes this problem. Version-Release number of selected component (if applicable): How reproducible: It's an intermittent problem, but usually easy to reproduce. Steps to Reproduce: 1. Create multiple widgets be refreshed every hour at 0 minute. 2. Wait for widget to refresh Actual results: Some widget will not get refreshed. My assumption is that the database data is getting generated at the same time the widget is getting refreshed causing some widget refresh to fail. Expected results: Widget should be refreshed properly even if schedule at 0 minute of every hour. Additional info:
Created attachment 1006807 [details] Widget
Actually, I have this problem even if widgets are scheduled later than every 0 minute of the hour. All the widgets on my screen capture were scheduled to refresh every hour. As you can see, they haven't been refreshed for multiple hours. There is no error in the task list. All my tasks status are "ok".
https://github.com/ManageIQ/manageiq/pull/5429
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/dd05cf3bf21f73523b15018592c9f185bd82fa17 commit dd05cf3bf21f73523b15018592c9f185bd82fa17 Author: Libor Pichler <lpichler@redhat.com> AuthorDate: Fri Nov 13 15:30:00 2015 +0100 Commit: Libor Pichler <lpichler@redhat.com> CommitDate: Mon Nov 16 10:04:37 2015 +0100 Fixing correct storing MiqExpression when new widget is created https://bugzilla.redhat.com/show_bug.cgi?id=1204826 app/controllers/report_controller/widgets.rb | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=ebb73403633f14593f10d55ebdf4cd47b225e16d commit ebb73403633f14593f10d55ebdf4cd47b225e16d Author: Libor Pichler <lpichler@redhat.com> AuthorDate: Wed Nov 18 12:46:29 2015 +0100 Commit: Libor Pichler <lpichler@redhat.com> CommitDate: Fri Dec 4 14:52:26 2015 +0100 Add spec for correct storing MiqExpression when new widget is created https://bugzilla.redhat.com/show_bug.cgi?id=1204826 .../miq_report_controller/widgets_spec.rb | 82 ++++++++++++++++++++++ 1 file changed, 82 insertions(+) create mode 100644 vmdb/spec/controllers/miq_report_controller/widgets_spec.rb
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=52d615f50f9d54df57cdeeba4133d1fd36d4d175 commit 52d615f50f9d54df57cdeeba4133d1fd36d4d175 Author: Libor Pichler <lpichler@redhat.com> AuthorDate: Wed Nov 18 12:47:51 2015 +0100 Commit: Libor Pichler <lpichler@redhat.com> CommitDate: Fri Dec 4 14:52:33 2015 +0100 Fixing correct storing MiqExpression when new widget is created https://bugzilla.redhat.com/show_bug.cgi?id=1204826 vmdb/app/controllers/report_controller/widgets.rb | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=968af1d81594529167db56bde231313b4e8adfd9 commit 968af1d81594529167db56bde231313b4e8adfd9 Author: Libor Pichler <lpichler@redhat.com> AuthorDate: Fri Nov 13 15:30:00 2015 +0100 Commit: Libor Pichler <lpichler@redhat.com> CommitDate: Wed Nov 18 12:56:03 2015 +0100 Fixing correct storing MiqExpression when new widget is created https://bugzilla.redhat.com/show_bug.cgi?id=1204826 (cherry picked from commit dd05cf3bf21f73523b15018592c9f185bd82fa17) app/controllers/report_controller/widgets.rb | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
Widget is able to refreshed properly even if schedule at 0 minute of every hour. Verified Version :- 5.6.0.4-beta2.3.20160421172650_719e256
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/RHBA-2016:1348