Bug 1574396

Summary: Utilization for random entities giving unexpected error for Record Not Found
Product: Red Hat CloudForms Management Engine Reporter: Nikhil Dhandre <ndhandre>
Component: UI - OPSAssignee: Hilda Stastna <hstastna>
Status: CLOSED WORKSFORME QA Contact: Nikhil Dhandre <ndhandre>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, dmetzger, hkataria, hstastna, lavenel, mpovolny, ndhandre, obarenbo
Target Milestone: GA   
Target Release: 5.10.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-18 14:56:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nikhil Dhandre 2018-05-03 08:14:15 UTC
Created attachment 1430554 [details]
log.tar.gz

Description of problem:
-----------------------
When I tried to open Utilization Page for some random entities like Host, VM unexpected error occurring. It is not able to reproduce every time however I have seen this three times before. Mostly second time I am able to access entities utilization page.

Yes, it is one of the possibility that record not found for the specific chart, but I am able to access the same thing the second time. Also, we have functionality that 'Utilization' tab active only if metrics available (It should be disabled in case record not available). 


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



How reproducible:
-----------------
Not always (10-20% times, I guess!)


Steps to Reproduce:
-------------------
1. Navigate to VM or Host
2. Try to open Utilization Page (Monitoring > Utilization)


Actual results:
---------------
It is raising an unexpected error.

ActiveRecord::RecordNotFound] Couldn't find MiqTask with 'id'=123

Expected results:
-----------------
It should not raise an unexpected error as I am able to access the same page the second time. 


Additional info:
----------------
Attaching logs and snapshot of an unexpected error.

Comment 7 Hilda Stastna 2019-02-18 14:37:03 UTC
This bug is not reproducible in latest release.