Bug 1391921 - Page 'Scale Infrastructure Provider Down' shows no compute nodes in stack
Summary: Page 'Scale Infrastructure Provider Down' shows no compute nodes in stack
Keywords:
Status: CLOSED DUPLICATE of bug 1390600
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-04 11:43 UTC by Oleksandr Kolisnyk
Modified: 2016-11-18 22:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 23:02:23 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screen of Scale Infrastructure Provider Down (82.29 KB, image/png)
2016-11-04 11:43 UTC, Oleksandr Kolisnyk
no flags Details

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 ***


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