Bug 1391921

Summary: Page 'Scale Infrastructure Provider Down' shows no compute nodes in stack
Product: Red Hat CloudForms Management Engine Reporter: Oleksandr Kolisnyk <okolisny>
Component: UI - OPSAssignee: Dan Clarizio <dclarizi>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: hkataria, jhardy, mpovolny, obarenbo, tzumainn
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-07 23:02:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screen of Scale Infrastructure Provider Down none

Description Oleksandr Kolisnyk 2016-11-04 11:43:37 UTC
Created attachment 1217380 [details]
Screen of Scale Infrastructure Provider Down

Description of problem:

On a CFME 5.7 + OSPD 10 setup, CFME appliance shows that chosen Infra-provider has no compute nodes when trying to scale it down.


How reproducible:
Always

Pre-conditions:
You should add OSPD10 with installed overcloud as Infrastructure provider to CFME 5.7

Steps to Reproduce:
1. Login to CF UI
2. Go Compute -> Infrastructure -> Providers
3. Click on appropriate provider's thumbnail
4. Go Configuration -> Scale this infrastructure provider down 

Actual results:
Opened page contains an empty table with no options to choose, label "Number of Compute Hosts" is "0"

Expected results:
Opened page contains table with options to choose particular compute node for further scale down of Infrastructure provider

Comment 2 Tzu-Mainn Chen 2016-11-04 15:11:39 UTC
I believe this is fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1390600

Comment 3 Oleksandr Kolisnyk 2016-11-07 23:02:23 UTC

*** This bug has been marked as a duplicate of bug 1390600 ***