Description of problem: After successfully installed the Operator, tried to create Custom Resource instance with "Edit Form" view, the Web Console crashed. Version-Release number of selected component (if applicable): 4.2.0-0.ci-2019-09-11-103058 How reproducible: 100% reproducible with "Dynatrace OneAgent Operator", "Akka Cluster Operator", "MariaDB", "MemSQL", and more. Steps to Reproduce: 1. Installed Operator from OperatorHub 2. Go to "Installed Operator" details view 3. Go to "Create Instance" view, switch to "Edit Form" view --> console crashed. Actual results: console crashed. Expected results: rendered creation form Additional info:
Could not reproduce on 4.2.0-0.ci-2019-09-12-015306 cluster. Could you please provide the version you hit the issue?
Uncaught TypeError: Cannot read property 'spec' of undefined at create-operand.tsx:151 at Array.map (<anonymous>) at CreateOperandForm (create-operand.tsx:144) at renderWithHooks (react-dom.development.js:12938) at mountIndeterminateComponent (react-dom.development.js:15020) at beginWork (react-dom.development.js:15625) at performUnitOfWork (react-dom.development.js:19312) at workLoop (react-dom.development.js:19352) at renderRoot (react-dom.development.js:19435) at performWorkOnRoot (react-dom.development.js:20342)
I can reproduce.
Sorry for the confusion. Can reproduce as well. But with different error: Uncaught TypeError: Cannot read property 'includes' of undefined at create-operand.tsx:161 at Array.some (<anonymous>) at create-operand.tsx:161 at Array.map (<anonymous>) at CreateOperandForm (create-operand.tsx:161) at renderWithHooks (react-dom.development.js:12938) at mountIndeterminateComponent (react-dom.development.js:15020) at beginWork (react-dom.development.js:15625) at performUnitOfWork (react-dom.development.js:19312) at workLoop (react-dom.development.js:19352)
payload 4.2.0-0.nightly-2019-09-15-052022 Checked on ocp 4.2 with above version, install MariaDB operator, then create mariadb instance with "Edit Form" view, could create successfully. The page doesn't crash. The bug has been fixed, so move it 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-2019:2922