Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-16736

‘Oh no! Something went wrong’ will be shown when user go to MultiClusterEngine details -> Yaml tab

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done-Errata
    • Major
    • 4.16.0
    • 4.14
    • Management Console
    • None
    • -
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when the Advanced Cluster Management for Kubernetes (ACM) and multicluster engine for Kubernetes (MCE) Operators are installed and their plugins are enabled, the yaml code Monaco editor failed to load.
      With this update, optional resource chaining was added to the to prevent a failed resource call, and the yaml editor no longer fails to load when the ACM and MCE Operators are installed and their plugins enabled. (link:https://issues.redhat.com/browse/OCPBUGS-16736[*OCPBUGS-16736*])
      Show
      * Previously, when the Advanced Cluster Management for Kubernetes (ACM) and multicluster engine for Kubernetes (MCE) Operators are installed and their plugins are enabled, the yaml code Monaco editor failed to load. With this update, optional resource chaining was added to the to prevent a failed resource call, and the yaml editor no longer fails to load when the ACM and MCE Operators are installed and their plugins enabled. (link: https://issues.redhat.com/browse/OCPBUGS-16736 [* OCPBUGS-16736 *])
    • Bug Fix
    • Done

    Description

      Description of problem:

          Oh no! Something went wrong’ will be shown when user go to MultiClusterEngine details -> Yaml tab

      Version-Release number of selected component (if applicable):

          4.14.0-0.nightly-2023-07-20-215234

      How reproducible:

          Always

      Steps to Reproduce:

      1. Install 'multicluster engine for Kubernetes' operator in the cluster
2. Use the default value to create a new MultiClusterEngine
3. Navigate to the MultiClusterEngine details -> Yaml Tab

         

      Actual results: 
‘Oh no! Something went wrong.’ error will be shown with below details
TypeErrorDescription:
 Cannot read properties of null (reading 'editor')  

      Expected results:

          no error 

      Additional info:

          This bug fix is in conjunction with https://issues.redhat.com/browse/OCPBUGS-22778

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-23205 [release-4.14] ‘Oh no! Something went wrong’ will be shown when user go to MultiClusterEngine details -> Yaml tab

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-23205 [release-4.14] ‘Oh no! Something went wrong’ will be shown when user go to MultiClusterEngine details -> Yaml tab

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is depended on by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-29812 [4.15] yaml tab crash on some browser versions when mce is installed

          • Undefined - Priority not specified.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-29813 [4.14] yaml tab crash on some browser versions when mce is installed

          • Undefined - Priority not specified.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-13842 Resource YAML page is keep crashing

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          GitHub openshift/console#13195: OCPBUGS-16736: use setTimeout to allow model to be created

          GitHub openshift/console#13510: OCPBUGS-16736: Addition of optional chaining to prevent yaml crash

          GitHub openshift/console#13646: OCPBUGS-16736: Release 4.14 backports

          Web Link RHEA-2023:7198 rpm

          Web Link RHSA-2023:7198 OpenShift Container Platform 4.15 security update

          Activity

            People

              sgoodwin_redhat Steve goodwin
              rhn-support-xiyuzhao Xiyun Zhao
              Xiyun Zhao Xiyun Zhao
              Votes:
              3 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: