| Summary: | Multiple errors =>"MIQ(MiqExpression#custom_attribute_columns_and_models) Cannot parse field MiqReport.id" | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Thomas Hennessy <thenness> | ||||||||
| Component: | Reporting | Assignee: | Gregg Tanzillo <gtanzill> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Niyaz Akhtar Ansari <nansari> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 5.7.0 | CC: | bascar, cpelland, jhardy, jistefan, obarenbo, thenness, yrudman | ||||||||
| Target Milestone: | GA | ||||||||||
| Target Release: | cfme-future | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | report:retest | ||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-08-23 18:37:58 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | CFME Core | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
Created attachment 1212182 [details]
full appliance logs from startup
Jiri, please try to reproduce this one on 5.6 and 5.7, thx. Created attachment 1213946 [details]
ruby module to schedule all reports for periodic execution
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. Closing this BZ since reported issue caused by custom testing script which is not part of product. |
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.