Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1328197 - Container overview page doesn't show any data when metrics needed fields are nil
Container overview page doesn't show any data when metrics needed fields are nil
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.5.0
All Linux
high Severity high
: GA
: 5.6.0
Assigned To: Ari Zellner
Einat Pacifici
container
: ZStream
Depends On:
Blocks: 1329298
  Show dependency treegraph
 
Reported: 2016-04-18 12:34 EDT by Christian Jung
Modified: 2018-07-30 05:10 EDT (History)
10 users (show)

See Also:
Fixed In Version: 5.6.0.5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1329298 (view as bug list)
Environment:
Last Closed: 2016-06-29 11:50:44 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
snaim: automate_bug+


Attachments (Terms of Use)
current logs (486.45 KB, application/x-bzip)
2016-04-18 12:48 EDT, Christian Jung
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 14:50:04 EDT

  None (edit)
Description Christian Jung 2016-04-18 12:34:33 EDT
Description of problem:
We managed to get OpenShift Enterprise 3.1 integrated into CloudForms and for a couple of days everything seemed fine. The Container Overview page did show Metriks and overall statistics of the infrastructure.

After a few days, the Overview page only shows "0" for all counters and the Metric Information is not displayed

Version-Release number of selected component (if applicable):
5.5.3

How reproducible:
we did setup two CF appliances and after a couple of days they were showing the same behavior.

Steps to Reproduce:
1. Add an OpenShift Enterprise provider
2. make sure OSE Metrics work
3. (in our case) after a few days, the overview page doesn't show metrics nor provider statistics

Additional info:
Navigating to the OSE Provider details, like the individual Pods, Services etc. delivers correct data. Also the topology map shows current data.
Comment 2 Christian Jung 2016-04-18 12:45:04 EDT
This is an extract from production.log which might be related to the problem:

[----] I, [2016-04-18T16:39:15.110683 #30346:66d988]  INFO -- : Completed 500 Internal Server Error in 143ms (Views: 56.1ms | ActiveRecord: 27.4ms)
[----] I, [2016-04-18T16:39:20.321064 #30346:66d988]  INFO -- : Started GET "/container_dashboard/data" for 88.128.81.207 at 2016-04-18 16:39:20 +0000
[----] I, [2016-04-18T16:39:20.323133 #30346:66d988]  INFO -- : Processing by ContainerDashboardController#data as HTML
[----] F, [2016-04-18T16:39:20.398341 #30346:66d988] FATAL -- : Error caught: [TypeError] nil can't be coerced into Fixnum
/var/www/miq/vmdb/app/services/container_dashboard_service.rb:174:in `+'
/var/www/miq/vmdb/app/services/container_dashboard_service.rb:174:in `block in ems_utilization'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/relation/delegation.rb:46:in `each'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/relation/delegation.rb:46:in `each'
/var/www/miq/vmdb/app/services/container_dashboard_service.rb:172:in `ems_utilization'
/var/www/miq/vmdb/app/services/container_dashboard_service.rb:16:in `all_data'
/var/www/miq/vmdb/app/controllers/container_dashboard_controller.rb:30:in `collect_data'
Comment 3 Christian Jung 2016-04-18 12:48 EDT
Created attachment 1148255 [details]
current logs
Comment 5 Ari Zellner 2016-04-19 07:46:00 EDT
upstream PR - https://github.com/ManageIQ/manageiq/pull/8080
Comment 9 Ari Zellner 2016-04-23 15:59:06 EDT
PR merged
Comment 15 errata-xmlrpc 2016-06-29 11:50:44 EDT
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

Note You need to log in before you can comment on or make changes to this bug.