Bug 1386749 - Multiple errors =>"MIQ(MiqExpression#custom_attribute_columns_and_models) Cannot parse field MiqReport.id"
Summary: Multiple errors =>"MIQ(MiqExpression#custom_attribute_columns_and_models) Can...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: Niyaz Akhtar Ansari
URL:
Whiteboard: report:retest
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 14:47 UTC by Thomas Hennessy
Modified: 2017-09-14 11:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-23 18:37:58 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
full log of process 611 log lines with error (60.01 KB, text/plain)
2016-10-19 14:47 UTC, Thomas Hennessy
no flags Details
full appliance logs from startup (6.55 MB, application/zip)
2016-10-19 14:50 UTC, Thomas Hennessy
no flags Details
ruby module to schedule all reports for periodic execution (1005 bytes, text/plain)
2016-10-25 15:00 UTC, Thomas Hennessy
no flags Details

Description Thomas Hennessy 2016-10-19 14:47:20 UTC
Created attachment 1212179 [details]
full log of process 611 log lines with error

Description of problem: problems apparently associated with memcache or storing into memcache


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


How reproducible: just starting up the appliance and running anything


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: problem presents in process # 611 which does not identify itself clearly.  complete grep of process 611 is provided.

Comment 2 Thomas Hennessy 2016-10-19 14:50:44 UTC
Created attachment 1212182 [details]
full appliance logs from startup

Comment 3 Dave Johnson 2016-10-24 17:33:04 UTC
Jiri, please try to reproduce this one on 5.6 and 5.7, thx.

Comment 5 Thomas Hennessy 2016-10-25 15:00:51 UTC
Created attachment 1213946 [details]
ruby module to schedule all reports for periodic execution

Comment 6 Thomas Hennessy 2016-10-25 15:03:39 UTC
I have attached a ruby program to this case which I suspect may be the cause of the reported issue.  Thiss program is not a part of the base product and therefore this BZ may be inappropriate.  Please note that the intent is to schedule the execution of all defined reports on a periodic basis.  In the version provided the reports are scheduled every 4 hours, but I have used this code to "assault" the builds for testing purposes to ensure that all reports are exercised at least during my testing.  My testing environment is a very small (< 30 VMs) VMware environment in the Raleigh GSS lab.

Comment 7 Yuri Rudman 2017-08-23 18:37:58 UTC
Closing this BZ since reported issue caused by custom testing script which is not part of product.


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