Description of problem: JavaScript errors in Camel-Profile tab in openshift-jvm console Version-Release number of selected component (if applicable): openshift-jvm Version: 1.0.50 How reproducible: always Steps to Reproduce: 1. Deploy some camel route to OCP (for example s2i-springboot-camel-amq: https://github.com/jboss-fuse/application-templates/blob/application-templates-2.0.fuse-000007/quickstarts/springboot-camel-amq-template.json) 2. Open Java console from pod page 3. Camel tab -> jms-cbr-route -> Profile 4. Open Web console in Firefox 5. You can see java scriot errors Actual results: Error: f.selectedItems is undefined .link/y@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:44:30199 r@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:6:1421 Sn/this.$get</f.prototype.$digest@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:6:2172 Sn/this.$get</f.prototype.$apply@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:6:3672 S@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:13:19620 o@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:66:12748 r/<.lcb@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:51:3822 n/</v.success@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:51:3374 s/<@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:51:4212 t/this.request/a.success@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:51:1692 Z.Callbacks/c@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:2:6426 Z.Callbacks/d.fireWith@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:2:7243 n@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:3:11930 .send/t/<@https://api.devel.xpaas:8443/console/java/libs-b80880b94c.js:3:17678 Expected results: no errors
Fix ready for testing. Please use openshift-jvm v1.0.51
in web console in https://github.com/openshift/origin-web-console/pull/858
This has been merged into ocp and is in OCP v3.4.0.25 or newer.
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-2017:0066