Description of problem: When the user has selected 'Layout 2' (internal called ColaForce layout) the topology crashes and catches an error: Could not find layout for type: ColaForce The old layout could be selected in 4.10 and is not available anymore in 4.11. Version-Release number of selected component (if applicable): 4.11 (master, tested with ea282e6a617b1a0638be23058a37c5914f3c8ccc) How reproducible: Always Steps to Reproduce: In theory, update a cluster from 4.10 to 4.11... Local development: 1. Checkout `branch-4.10`, build it, run it 2. Import an application, open the topology graph view and switch to Layout 2 3. Checkout `branch-4.11`, or master, build it, run it. 4. Re-open or refresh your browser and open the same namespace Or setting the ConfigMap manually: 1. Search in the namespace "openshift-console-user-settings" for the user settings ConfigMap of your user. 2. Override this topology YAML (replace sidebar1 with your namespace): devconsole.topology.layout: '{"sidebar1":{"nodes":[],"layout":"ColaForce"}}' Actual results: Topology crashes with error: Could not find layout for type: ColaForce Expected results: Topology should not crash and should unset the removed layout Additional info:
Verified on 4.11.0-0.nightly-2022-05-20-213928
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069