Bug 1271905 - [RFE]For Amazon EC2 instances, capture the Last Boot Time.
Summary: [RFE]For Amazon EC2 instances, capture the Last Boot Time.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: James Wong
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ec2
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-15 04:46 UTC by Nikhil Gupta
Modified: 2019-08-15 05:40 UTC (History)
9 users (show)

Fixed In Version: 5.6.0.8
Doc Type: Bug Fix
Doc Text:
There was a request to capture the last boot time in CloudForms user interface for Amazon EC2 instances; this has been implemented with this update.
Clone Of:
Environment:
Last Closed: 2016-06-29 15:00:27 UTC
Category: Feature
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Nikhil Gupta 2015-10-15 04:46:23 UTC 
Description of problem:
[RFE]For Amazon EC2 instances, capture the Last Boot Time in Cloudforms UI.

Currently it is showing as N/A. I assume it is because cfme do not captures instance event timelines for Amazon EC2.
Comment 2 Dave Johnson 2015-10-26 19:02:14 UTC 
From the bug triage, setting H/H
Comment 3 James Wong 2016-05-12 14:17:38 UTC 
PR created https://github.com/ManageIQ/manageiq/pull/8639
Comment 4 Matouš Mojžíš 2016-05-26 12:26:51 UTC 
Verified in 5.6.0.8-rc1.20160524155303_f2a5a50.
Last Boot Time was displayed correctly.
Comment 6 errata-xmlrpc 2016-06-29 15:00: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.

https://access.redhat.com/errata/RHBA-2016:1348
Note You need to log in before you can comment on or make changes to this bug.