Bug 1441272 - queue_name_for_metrics_collection raises an exception when ems is nil
Summary: queue_name_for_metrics_collection raises an exception when ems is nil
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: C&U Capacity and Utilization
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.7.3
Assignee: Adam Grare
QA Contact: Einat Pacifici
Depends On: 1439888
TreeView+ depends on / blocked
Reported: 2017-04-11 14:18 UTC by Satoe Imaishi
Modified: 2020-06-11 13:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1439888
Last Closed: 2017-06-28 14:59:55 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1601 0 normal SHIPPED_LIVE Important: CFME 5.7.3 security, bug fix and enhancement update 2017-06-28 18:51:52 UTC

Comment 2 Adam Grare 2017-04-11 15:36:06 UTC
Customer is observing containers with nil ems_id and old_ems_id being created as of today, requesting a hotfix for this issue.

Comment 3 CFME Bot 2017-04-11 20:31:02 UTC
New commit detected on ManageIQ/manageiq/euwe:

commit add1b9465d0b8c292b5b6e17cc8a3a4ce6c54d17
Author:     Jason Frey <fryguy9@gmail.com>
AuthorDate: Mon Apr 10 17:50:10 2017 -0400
Commit:     Satoe Imaishi <simaishi@redhat.com>
CommitDate: Tue Apr 11 16:23:21 2017 -0400

    Merge pull request #14718 from agrare/bz_1439888_metrics_collection_nil_queue_name
    Handle exception when a metrics target doesn't have an ext_management_system
    (cherry picked from commit d7a82f2b0ccf7ca3394fe73bfa768b4417698ae5)

 app/models/metric/capture.rb                | 10 +++++++---
 app/models/metric/ci_mixin/capture.rb       | 23 ++++++++++++-----------
 spec/models/metric/ci_mixin/capture_spec.rb |  6 +++---
 3 files changed, 22 insertions(+), 17 deletions(-)

Comment 6 errata-xmlrpc 2017-06-28 14:59:55 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.


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