Bug 1669851 - [RFE][PRD] As an operator, I must be able to see the current firmware landscape on the system
Summary: [RFE][PRD] As an operator, I must be able to see the current firmware landsca...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: MVP
: 5.11.0
Assignee: Tadej Borovšak
QA Contact: Tadej Borovšak
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-27 15:16 UTC by Matej Artac
Modified: 2019-12-12 13:35 UTC (History)
5 users (show)

Fixed In Version: 5.11.0.15
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:34:59 UTC
Category: Feature
Cloudforms Team: Redfish
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:35:14 UTC

Description Matej Artac 2019-01-27 15:16:22 UTC
RFE: As an operator, I must be able to see the current firmware landscape on the system: BIOS, BMC (if relevant) and storage controller in the UI.

Comment 2 Matej Artac 2019-07-12 10:48:42 UTC
For the vendors that comply with Redfish standard FirmwareInventory, we have now implemented the display of the list of firmware updates installed in the system. The physical system overview contains the list of all the known firmwares and their version/revision number.

Related PR:
  * https://github.com/ManageIQ/manageiq-providers-redfish/pull/83

Comment 4 errata-xmlrpc 2019-12-12 13:34:59 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-2019:4199


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