Description of problem: When loading environment variable editors in Deploy Image page, blank page returned Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-09-03-102130 How reproducible: Always Steps to Reproduce: 1. User create a project, then goes to Developer Console 2. Choose Container Image from developer catalog 3. Set Image Name as 'aosqe/hello-openshift' and search 4. Click on 'Deployment Configuration' in Advanced Options Actual results: 4. page goes to blank and js error returned TypeError: "this.currentEnvVars[e] is undefined" getEnvVarByTypeAndIndex dev-console-deployImage-chunk-3662c14942e6dcc11a41.min.js:1 render dev-console-deployImage-chunk-3662c14942e6dcc11a41.min.js:1 ki vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 Ti vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 Mi vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 Va vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 qa vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 ku vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 Au vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 wu vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 Ja vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 enqueueSetState vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122348 setState vendors~main-chunk-bff8b847536bfce9e9ef.min.js:122313 componentDidMount dev-console-deployImage-chunk-3662c14942e6dcc11a41.min.js:1 a vendors~main-chunk-bff8b847536bfce9e9ef.min.js:117464 j vendors~main-chunk-bff8b847536bfce9e9ef.min.js:117464 l vendors~main-chunk-bff8b847536bfce9e9ef.min.js:117464 backend.js:1:11464 Expected results: 4. there should be no errors Additional info:
https://jira.coreos.com/browse/ODC-1754
When click on 'Deployment Configuration' or 'Build Configuration' in Advanced Options, environment variable editors can be loaded successfully. User can add key/value & values from configmap/secret successfully Verified on 4.2.0-0.nightly-2019-09-10-181551
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-2019:2922