Bug 1242312
| Summary: | Template using Custom BuildConfig causes JavaScript error in Console | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Andrew Block <andrew.block> | ||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yanping Zhang <yanpzhan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.0.0 | CC: | adellape, jliggitt, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, pruan, wsun | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openshift-3.0.1.0-1.git.388.51e9da7.el7ose | Doc Type: | Bug Fix | ||||
| Doc Text: |
The web console previously produced errors when users attempted to create from templates that had a Custom build strategy. The errors obscured the template parameters from being shown or managed. The web console has now been updated to properly handle Custom and Docker build strategies in templates. As a result, the errors no longer occur, and template parameters can be viewed and managed.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-03 20:17:38 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: | |||||||
| Attachments: |
|
||||||
*** Bug 1242313 has been marked as a duplicate of this bug. *** I can reproduce. Un-minified stack:
TypeError: Cannot read property 'namespace' of undefined
at resources.js:273
at newfromtemplate.js:36
at Object.forEach (angular.js:323)
at imageItems (newfromtemplate.js:34)
at newfromtemplate.js:168
at processQueue (angular.js:13170)
at angular.js:13186
at Scope.$eval (angular.js:14383)
at Scope.$digest (angular.js:14199)
at Scope.$apply (angular.js:14488)
Reproduced the issue on ose3.0.0.1: 1.Create template in project. $oc create -f origin/example/sample-app/application-template-custombuild.json templates/ruby-helloworld-sample 2.On web console, open the developer tool, and monitor the console.create app with template ruby-helloworld-sample. On the creation page, parameters in the template can not be shown and managed, and could see the error in console: TypeError: Cannot read property 'namespace' of undefined Verified the bug on ose3.0.1.0 with version v3.0.1.0-388-g51e9da7. 1.Create template in project. $oc create -f origin/example/sample-app/application-template-custombuild.json templates/ruby-helloworld-sample 2.On web console, open the developer tool, and monitor the console.create app with template ruby-helloworld-sample. The parameters in the template can be viewed and managed. There is no TypeError in console now. 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-2015:1540 |
Created attachment 1051271 [details] Template with custom buildconfig Description of problem: If a custom BuildConfig in defined in a template, when attempting to use the template during the creation of an application from a template, an JavaScript error occurs obscuring the template parameters from being displayed or modified. The following error is shown in the Chrome (43.0.2357.132 64bit) developer console referencing vendor.js (5301) TypeError: Cannot read property 'namespace' of undefined at scripts.js:2557 at scripts.js:1600 at Object.f [as forEach] (vendor.js:3208) at n (scripts.js:1598) at scripts.js:1671 at i (vendor.js:5547) at vendor.js:5555 at l.$get.l.$eval (vendor.js:5835) at l.$get.l.$digest (vendor.js:5792) at l.$get.l.$apply (vendor.js:5857) The template can still be instantiated successfully from the oc CLI tool Version-Release number of selected component (if applicable): OpenShift Enterprise 3.0.0 How reproducible: Always Steps to Reproduce: 1. Use Template with custom BuildConfig strategy 2. Using web console, create a new application using the template. 3. JS error occurs where parameters can not be managed Actual results: JavaScript error occurs when creating an application from a template with a Custom BuildConfig Expected results: Parameters in a template can be viewed and modified in the web console Additional info: