Bug 1364195

Summary: Undercloud Hosts missing power state and CPU information
Product: Red Hat CloudForms Management Engine Reporter: Kevin Morey <kmorey>
Component: ProvidersAssignee: Tzu-Mainn Chen <tzumainn>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: david.costakos, jfrey, jhajyahy, jhardy, kmorey, nstephan, obarenbo, simaishi, vestival, wrichter
Target Milestone: GA   
Target Release: 5.7.0   
Hardware: All   
OS: All   
Whiteboard: openstack:host
Fixed In Version: 5.7.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-04 12:59:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Kevin Morey 2016-08-04 16:43:43 UTC
Created attachment 1187575 [details]
screenshot

Description of problem:
Undercloud hosts missing power state and CPU information even after a successful smart-state analysis is ran. I have tested this on a 5.6.0.13 as well as a 5.6.1.0 appliance.

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

How reproducible:
everytime

Steps to Reproduce:
1. Navigate to Undercloud provider / hosts
2. select a host to view the summary page
3. kick off a SSA if you want.
4. you will see power state and CPU data missing. (Memory is there though)

Actual results:
missing data

Expected results:
to see relevant CPU, Cores and power state

Additional info:
see screenshot

Comment 2 david.costakos 2016-08-09 14:18:13 UTC
*** Bug 1365554 has been marked as a duplicate of this bug. ***

Comment 3 Tzu-Mainn Chen 2016-11-03 19:19:37 UTC
should be fixed by https://github.com/ManageIQ/manageiq/pull/8466

Comment 4 Ronnie Rasouli 2016-11-13 12:58:05 UTC
verified by automation on 5.7.0.10

Comment 6 errata-xmlrpc 2017-01-04 12:59:05 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://rhn.redhat.com/errata/RHBA-2017-0012.html