Bug 1389479

Summary: [beta1] SSUI missing IP Address and hostname in services summary page
Product: Red Hat CloudForms Management Engine Reporter: Kevin Morey <kmorey>
Component: UI - ServiceAssignee: Allen W <awight>
Status: CLOSED NEXTRELEASE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: dclarizi, jhardy, kmorey, nstephan, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-28 16:35:57 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
screenshot none

Description Kevin Morey 2016-10-27 16:44:37 UTC
Created attachment 1214674 [details]
screenshot

Description of problem:
As a self service user i cannot tell how to connect to my application after it is deployed using the SSUI since 

Version-Release number of selected component (if applicable):
5.7.0.7-beta1.20161025153249_9376fbd

How reproducible:
100%

Steps to Reproduce:
1. log into ssui
2. navigate to a service
3. review the list of vm(s) in the service

Actual results:

no connectivity information is there thus preventing the end user the ability to log into their applicaiton.

Expected results:
Expected to see the VMs IP and hostname so that one may SSH/RDP to it.

Additional info:
see screenshot

Comment 3 Allen W 2016-10-28 14:26:24 UTC
`http://localhost:3000/api/services?expand=resources&attributes=picture,picture.image_href,evm_owner.name,v_total_vms,chargeback_report&filter[]=service_id=nil`


🖕🏾 is the call to pull in services (that sui is using) does not have ip addy info on the response we're gonna redo this whole capability in the sui for the next release, so i wanta call this a not bug as it will be addressed as sui services is brought to ops services parity

Comment 4 Allen W 2016-10-28 16:35:57 UTC
As previous comment mentioned, this'll be addressed as sui meets opsui parity.