Bug 1398685

Summary: Infrastructure provider properties show zero CPU capacity
Product: Red Hat CloudForms Management Engine Reporter: Oleksandr Kolisnyk <okolisny>
Component: UI - OPSAssignee: Marek Aufart <maufart>
Status: CLOSED WONTFIX QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: hkataria, jhardy, maufart, mpovolny, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-20 11:54:55 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:
Attachments:
Description Flags
provider properties scrn none

Description Oleksandr Kolisnyk 2016-11-25 14:53:05 UTC
Created attachment 1224375 [details]
provider properties scrn

Description of problem:
RHOS 9 undercloud added as infrastructure provider, determine any CPU info of nodes as '0'

Version-Release number of selected component (if applicable):
RHOS 9 + CFME 5.6.3.2

How reproducible:
Always


Steps to Reproduce:
1. Add a valid Openstack infrastructure provider
2. Go Compute -> Infrastructure -> Providers
3. Click on your provider's thumbnail icon
4. Check values 'Aggregate Node CPU Resources', 'Aggregate Node CPUs', 'Aggregate Node CPU Cores' at 'Properties' area
5. Click on 'Nodes' link at 'Relantionships' area
6. Click on any node icon
7. Check values 'Number of CPUs', 'Number of CPU Cores', 'CPU Cores Per Socket' at 'Properties' area

Actual results:
step 4, 7 - all values are equal to zero

Expected results:
All CPU properties show correct values

Comment 2 Oleksandr Kolisnyk 2017-02-08 15:10:40 UTC
UPD. Reproduced it on CFME 5.6.4.0 with RHOS 7

Comment 3 Oleksandr Kolisnyk 2017-02-17 19:30:26 UTC
Also reproduced it on 5.7.1.2 with RHOS 8

Comment 5 Josh Carter 2018-09-20 11:54:55 UTC
Bug Closure

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!