Bug 1666672
| Summary: | contextDirectory parameter is set to default value after setting it to empty. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Saurabh Sadhale <ssadhale> |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
| Status: | CLOSED DUPLICATE | QA Contact: | Yadan Pei <yapei> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.10.0 | CC: | aos-bugs, jokerman, mmccomas, wzheng |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-16 14:59:42 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: | |
| Embargoed: | |||
I think this has come up before, the console needs a way to distinguish "the user didn't touch this field, use the default from the template" and "the user explicitly set this to emptystring, pass emptystring as the parameter value" *** This bug has been marked as a duplicate of bug 1605136 *** |
Description of problem: While using the S2I catalog from Web Console, and using these following JBoss EAP 7.1 (no https), JBoss Web Server 3.1 Apache Tomcat 8 (no https). Setting the parameter to contextDir as empty does point it to the default location. Version-Release number of selected component (if applicable): 3.10 How reproducible: 1. Login to the OpenShift Web Console. 2. Select from the Service Catalog the image of "JBoss EAP 7.1(no https) ". 3. Add the required parameters and keep the contextDir parameter in the Configuration window as empty. 4. Check in the Build Config we will be able to see value is set to default. Steps to Reproduce: 1. 2. 3. Actual results: It should disappear. Expected results: It is still visible as default value. Additional info: 1. If in a project we have 1 application for 1 repository where the code is located in the root directory. There are no sub-directories so the row "contextDir: ${CONTEXT_DIR}" is present in the yaml but it shouldn't be there.