Bug 1391683

Summary: "Application Name" in Objects section does not get resolved properly, displays "${APPLICATION_NAME}" instead
Product: Red Hat CloudForms Management Engine Reporter: Ramesh A <rananda>
Component: UI - OPSAssignee: zakiva
Status: CLOSED NOTABUG QA Contact: Dafna Ron <dron>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: bazulay, fsimonce, hkataria, jhardy, mpovolny, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:container
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-15 20:43:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Application Name issue none

Description Ramesh A 2016-11-03 18:42:40 UTC
Created attachment 1217116 [details]
Application Name issue

Description of problem:
"Application Name" in Objects section does not get resolved properly, displays "${APPLICATION_NAME}" instead

Version-Release number of selected component (if applicable):
5.7.0.9-beta2.1.20161101182054_eb0afaa

How reproducible:
Very

Steps to Reproduce:
1. Manage a Container (say Openshift)
2. Navigate to Compute ==> Containers ==> Container Template ==> Click on any Template
3. Observe the Application name in "Name" column under "Objects" section

Actual results:
Displays "${APPLICATION_NAME}" instead of resolving to application name. Refer to the screenshot for further information

Expected results:
Should resolve to the appropriate application name

Additional info:

Comment 2 zakiva 2016-11-13 09:29:05 UTC
From my point of view the current behavior is the expected one because:
1. "${APPLICATION_NAME}" is a template parameter, by displaying it this way the user is notified regarding the use of a parameter in this field. So one can know that the parameter value can be changed, used in other fields, etc. 
Also, the value of the parameter can found at the parameters table below.  
2. In case that the parameter does not have a value (hasn't been set yet or auto-generated by openshift), we can't "resolve" it and display a value instead. 

This of course can be changed if another way is preferred. Barak, Federico what do you think?

Comment 3 Federico Simoncelli 2016-11-15 20:43:17 UTC
Current output is correct. What the user should see is the variable names. The values are filled in at instantiation time.

Closing.