Bug 1275404 - Icon images broken for timeline events
Summary: Icon images broken for timeline events
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.5.0
Assignee: Harpreet Kataria
QA Contact: Nandini Chandra
Depends On:
TreeView+ depends on / blocked
Reported: 2015-10-26 19:55 UTC by Nandini Chandra
Modified: 2015-12-08 13:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-12-08 13:40:27 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
screen shot of timelines page (95.77 KB, image/png)
2015-10-26 19:55 UTC, Nandini Chandra
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Nandini Chandra 2015-10-26 19:55:12 UTC
Created attachment 1086577 [details]
screen shot of timelines page

Description of problem:
Icon images don't get loaded for timeline events. I see this issue on both FF and Chrome.Refer to the attached screenshot.

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

How reproducible:

Steps to Reproduce:
1.Manage an infra or cloud provider.
2.Generate an event for the provider(Eg, powering on/off a VM)
3.From the summary page of the provider,click Monitoring, then click Timelines.

Actual results:
Icon images are broken for timeline events.

Expected results:
Icon images should get loaded for timeline events.

Additional info:

Comment 3 Nandini Chandra 2015-11-18 21:14:06 UTC
Verified in

Comment 5 errata-xmlrpc 2015-12-08 13:40:27 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.