Bug 1333165
Summary: | after creating from a template in console, no idea what values generated parameters got | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jessica Forrester <jforrest> |
Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.2.0 | CC: | aos-bugs, jokerman, mmccomas, tdawson, vdinh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-27 09:32:12 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: |
Description
Jessica Forrester
2016-05-04 20:02:50 UTC
Hi, The username and password for DBs are listed under environment section when you click on the deployment of the DBs. Those values will always be there so there is no need to make a note or anything. However, we can better document where the values are, that would be help. Thanks, Vu This is not necessarily true, the parameters can affect anything in the template, not just environment variables. We are also inconsistent with the CLI here, the CLI tells you what any generated parameters were set to. Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/5dab3ef2434012cc11a73c67357ebeebe03bb3bc Bug 1333165 - after creating from a template in console, no idea what values generated parameters got This is now fixed in OCP3.3 v3.3.0.7 After creating app from template, "Applied Parameter Values" on next step page will show all parameters and telling which parameters are generated automatically. May I verify this against OCP 3.3 ? I saw this is opened against OCP 3.2 Yes, we are not going to backport the fix for this. I'll set the target release to 3.3 Thanks, move to VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1933 |