Bug 1445702 - Unable to generate report for middleware servers
Summary: Unable to generate report for middleware servers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Edgar Hernández
QA Contact: Prachi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-26 10:38 UTC by Prachi
Modified: 2018-07-25 15:56 UTC (History)
8 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 13:12:04 UTC
Category: Bug
Cloudforms Team: Middleware
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Error staus while generaing reports (194.88 KB, image/png)
2017-04-26 10:38 UTC, Prachi
no flags Details
Screenshot_report_generated (108.27 KB, image/png)
2017-10-24 07:33 UTC, Sunil Kondkar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Description Prachi 2017-04-26 10:38:04 UTC
Created attachment 1274170 [details]
Error staus while generaing reports

Description of problem:

Unable to generate Performance reports for Middleware servers.

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

5.8.0.12-rc1.20170425180304_4f35996 

How reproducible:


Steps to Reproduce:
1. Login to CFME
2. Navigate to cloud Intel >> Reports
3. Select Reports >> Performance by Asset Type->Middleware servers
4. Click on the link for 'Transactions Pool - Hourly over last day'
​​5. Click on 'Queue' button at top left on the screen to generate the report 

Actual results:

Not Able to generate report and giving status error. Please refer attached screen-shot

Expected results: Should generate reports.


Additional info:

Getting Error in CFME logs:

*****************************
[----] W, [2017-04-26T06:35:13.722537 #3035:3e3140]  WARN -- : <AuditFailure> MIQ(Async.rescue in _async_generate_table) userid: [admin] - Either the metrics or the tags property must be set
[----] E, [2017-04-26T06:35:13.725315 #3035:3e3140] ERROR -- : MIQ(MiqQueue#deliver) Message id: [6259], Error: [Either the metrics or the tags property must be set]
[----] E, [2017-04-26T06:35:13.725477 #3035:3e3140] ERROR -- : [Hawkular::BaseClient::HawkularException]: Either the metrics or the tags property must be set  Method:[rescue in deliver]
[----] E, [2017-04-26T06:35:13.725547 #3035:3e3140] ERROR -- : /opt/rh/cfme-gemset/gems/hawkular-client-2.8.0/lib/hawkular/base_client.rb:217:in `handle_fault'
/opt/rh/cfme-gemset/gems/hawkular-client-2.8.0/lib/hawkular/base_client.rb:54:in `rescue in http_post'

*****************************

Comment 4 CFME Bot 2017-05-05 14:24:12 UTC
New commit detected on ManageIQ/manageiq-gems-pending/master:
https://github.com/ManageIQ/manageiq-gems-pending/commit/d065caf447aec788c55538583b571085a3bd24b7

commit d065caf447aec788c55538583b571085a3bd24b7
Author:     Edgar Hernández <ehernand>
AuthorDate: Thu May 4 12:27:33 2017 -0500
Commit:     Edgar Hernández <ehernand>
CommitDate: Thu May 4 12:30:30 2017 -0500

    Update hawkular client version to ~>3.0.2.
    
    There is a bug in 3.0.1 that was fixed in 3.0.2. Also, using "~>"
    instead of "=" to avoid updating the dependencies for each
    micro-release.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1445702

 manageiq-gems-pending.gemspec | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 5 CFME Bot 2017-05-07 08:51:27 UTC
New commit detected on ManageIQ/manageiq-providers-hawkular/master:
https://github.com/ManageIQ/manageiq-providers-hawkular/commit/83ea8b807ad1fd7bb5181219d793e518f1502eaf

commit 83ea8b807ad1fd7bb5181219d793e518f1502eaf
Author:     Edgar Hernández <ehernand>
AuthorDate: Thu May 4 11:08:20 2017 -0500
Commit:     Edgar Hernández <ehernand>
CommitDate: Thu May 4 12:20:36 2017 -0500

    Don't attemp to query Hawkular if no metrics were provided
    
    Hawkular returns with an error status code if an empty list of metrics
    is sent in the query. Indeed, it doesn't make sense to query the
    hawkular server if no metrics were requested and, instead, an empty
    object can be returned.
    
    One use case where this method is used, is when generating performance
    reports for middleware servers. If there is one server that has never been
    in running state or has been down for a "long" time, it may not have any
    metrics (all them may have expired and purged). If this happens, the
    "metrics" argument of collect_stats_metrics will be empty.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1445702

 .../providers/hawkular/middleware_manager/live_metrics_capture.rb        | 1 +
 1 file changed, 1 insertion(+)

Comment 6 Sunil Kondkar 2017-10-24 07:32:18 UTC
Verified on 5.9.0.2.20171010190026_0413a06

Report is generated successfully without error. Please refer the attached screenshot.

Comment 7 Sunil Kondkar 2017-10-24 07:33:53 UTC
Created attachment 1342545 [details]
Screenshot_report_generated

Comment 10 errata-xmlrpc 2018-03-01 13:12:04 UTC
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/RHSA-2018:0380


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