Bug 1827538 - console page turned to be blank when input colon in yaml editor
Summary: console page turned to be blank when input colon in yaml editor
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Jon Jackson
QA Contact: Yadan Pei
URL:
Whiteboard:
: 1828471 (view as bug list)
Depends On:
Blocks: 1829869
TreeView+ depends on / blocked
 
Reported: 2020-04-24 06:47 UTC by shahan
Modified: 2020-07-13 17:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Manifested, discovered, and fixed before release.
Clone Of:
Environment:
Last Closed: 2020-07-13 17:30:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5237 0 None closed Bug 1827538: Fix create operand yaml editor runtime error 2020-06-29 02:46:01 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:31:19 UTC

Description shahan 2020-04-24 06:47:46 UTC
Description of problem:
console page turned to be blank when input yaml editor. It appears this error occurs only for yaml editor of operand

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-04-21-103613


How reproducible:
Always

Steps to Reproduce:
1. Intall operator and goto it's operand creation page. here such as logging operator.
2. click create "Create ClusterLogging" and then change to yaml view
3. try to input the char ":" 

Actual results:
3. The console turned to be blank, below is the js error:
5-chunk-2437f5100010a5c8ec0d.min.js:1 Uncaught Error: Model is disposed!

Error: Model is disposed!
    at t._assertNotDisposed (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at t.getVersionId (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at t._deltaDecorationsImpl (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at t._setTrackedRange (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at e._updateTrackedRange (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at e.startTrackingSelection (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at e.startTrackingSelections (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at t.trigger (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at t.trigger (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at t.runCommand (5-chunk-2437f5100010a5c8ec0d.min.js:1)
    at 5-chunk-2437f5100010a5c8ec0d.min.js:1
(anonymous) @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
setTimeout (async)
unexpectedErrorHandler @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
e.onUnexpectedError @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
s @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
(anonymous) @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
(anonymous) @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
setTimeout (async)
(anonymous) @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
dispatchEvent @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
E @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
n.Class.define.cancel @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
wrapError @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
e.executeCommand @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
type @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
e.type @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
(anonymous) @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
e.fire @ 5-chunk-2437f5100010a5c8ec0d.min.js:1
(anonymous) @ 5-chunk-2437f5100010a5c8ec0d.min.js:1


Expected results:
The yaml editor should work well

Additional info:

Comment 1 Jon Jackson 2020-04-28 20:08:54 UTC
*** Bug 1828471 has been marked as a duplicate of this bug. ***

Comment 4 shahan 2020-05-09 03:07:58 UTC
No runtime error when input ':' in the yaml editor
4.5.0-0.nightly-2020-05-08-200452

Comment 5 errata-xmlrpc 2020-07-13 17:30:56 UTC
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-2020:2409


Note You need to log in before you can comment on or make changes to this bug.