Bug 1394485

Summary: Service : Click on stack from service Page shows "Invalid Input"
Product: Red Hat CloudForms Management Engine Reporter: Shveta <sshveta>
Component: UI - OPSAssignee: lgalis
Status: CLOSED CURRENTRELEASE QA Contact: Jeff Teehan <jteehan>
Severity: high Docs Contact:
Priority: high    
Version: 5.7.0CC: dajohnso, hkataria, jhardy, mpovolny, obarenbo, sshveta
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: stack:error
Fixed In Version: 5.8.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1411373 (view as bug list) Environment:
Last Closed: 2017-06-12 17:53:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1411373    
Attachments:
Description Flags
invalid input
none
input
none
stack service none

Description Shveta 2016-11-12 12:53:03 UTC
Created attachment 1220011 [details]
invalid input

Description of problem:


Version-Release number of selected component (if applicable):
5.7.0.10-beta3.20161109111947_9a61b18 

How reproducible:


Steps to Reproduce:
1. Create an orchestration stack 
2. From Myservice : go to that service and click on orchestration stack
3. It navigates to Compute stack page and shows "Invalid Input" as in screenshot

Actual results:


Expected results:


Additional info:

Comment 5 Shveta 2016-12-06 11:29:18 UTC
Created attachment 1228418 [details]
input

Comment 6 Shveta 2016-12-06 11:31:42 UTC
Created attachment 1228420 [details]
stack service

The stack is RHOS stack.
Also please note that it failed to create .
https://10.8.198.252 , servicename : heatsatck-20161206-062052

Comment 7 lgalis 2016-12-06 20:54:44 UTC
Hi Shveta - 

I have created a service myself in your appliance based on an existing orchestration stack - I do not see the problem you are reporting.
I then looked at your service - and the stack you have added, 'stackoheat' - does not exist. This is the reason why the link from the service for the orchestration stack is incorrect - because a stack with that name does not exist.

We could check with the Openstack ManageIq team to see if it would make sense to add a check for the existence of the stack at the time the service is created and if so, open a backend BZ for that.

Thanks,
Laura

Comment 8 Shveta 2016-12-07 10:39:23 UTC
That's right , the stack does not exist.
So may be the stack link in service page should be disabled if the stack fails to create.

Comment 11 Jeff Teehan 2017-04-24 22:03:18 UTC
The status I used created just fine, and when I clicked on the icon I got the details page.  Appears to be working fine in 5.8.0.11  Moving to verified.