Bug 1413654 - many vm create/remove/stop/start Azure events are absent in timelines though present in DB
Summary: many vm create/remove/stop/start Azure events are absent in timelines though ...
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.6.4
Assignee: Bronagh Sorota
QA Contact: Ievgen Zapolskyi
Whiteboard: provider:event:azure:timeline
Depends On: 1390587
TreeView+ depends on / blocked
Reported: 2017-01-16 15:52 UTC by Satoe Imaishi
Modified: 2017-03-09 17:07 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1390587
Last Closed: 2017-03-09 17:07:48 UTC
Category: ---
Cloudforms Team: Azure
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0474 0 normal SHIPPED_LIVE CFME 5.6.4 bug fixes and enhancement update 2017-03-09 22:03:14 UTC

Comment 2 CFME Bot 2017-01-16 18:36:13 UTC
New commit detected on ManageIQ/manageiq/darga:

commit 7afa8faee5d96340b073a210cd96179bc8e5b0d0
Author:     Greg Blomquist <blomquisg@gmail.com>
AuthorDate: Fri Nov 18 12:09:40 2016 -0500
Commit:     Satoe Imaishi <simaishi@redhat.com>
CommitDate: Mon Jan 16 13:31:24 2017 -0500

    Merge pull request #10 from bronaghs/event_not_mapped_to_vm_bz1390587
    Update the case of the Azure event vm_ems_ref property
    (cherry picked from commit f616de944c13e2b50e3146597cd57b58c2579b9d)

 app/models/manageiq/providers/azure/event_catcher_mixin.rb            | 4 ++--
 .../providers/azure/cloud_manager/event_catcher/runner_spec.rb        | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

Comment 4 errata-xmlrpc 2017-03-09 17:07:48 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.