Bug 1573804 - [online-int]No value for parameter APPLICATION_USER in caching-service template
Summary: [online-int]No value for parameter APPLICATION_USER in caching-service template
Keywords:
Status: NEW
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-02 09:55 UTC by wewang
Modified: 2018-05-03 01:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description wewang 2018-05-02 09:55:44 UTC
Description of problem:
No value for parameter APPLICATION_USER in template 

Version-Release number of selected component (if applicable):
v3.9.14 (online version 3.6.0.90)

How reproducible:
always
Steps to Reproduce:
1.oc new-app caching-service
error: error processing template "openshift/caching-service": Template.template.openshift.io "caching-service" is invalid: template.parameters[4]: Required value: template.parameters[4]: parameter APPLICATION_USER is required and must be specified

2.
3.

Actual results:
No value for parameter APPLICATION_USER in template 

Expected results:
should have value for parameter APPLICATION_USER 

Additional info:

Comment 1 Abhishek Gupta 2018-05-02 15:53:43 UTC
When using the console to deploy the template, the "Client User" field is required and the user cannot proceed without specifying it. However, when using the CLI, it is not very apparent that the user needs to specify the parameter (APPLICATION_USER) value and gets this error. The solution could simply be to provide a default value for this parameter (something like admin or caching-admin). Given most users will create applications using this template via the console (at least initially), I am not going to consider this a blocker.


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