Created attachment 1869237 [details] App Launcher with two sections that should be one Description of problem: Version-Release number of selected component (if applicable): 4.11, latest How reproducible: Apply a ConsoleLink CRD for the ApplicationMenu (or install an operator that does, like CodeReady Workspaces in this case) with slightly different casing in a section heading than what's already in the menu. It won't be combined with the first. Steps to Reproduce: 1. Apply a ConsoleLink CRD for the ApplicationMenu with a section value that has slightly different casing 2. Open the menu 3. Note that the two sections aren't combined Actual results: They're not combined Expected results: They should be combined Additional info: See this relevant Slack discussion: https://coreos.slack.com/archives/C6A3NV5J9/p1648468329861799?thread_ts=1648059105.807959&cid=C6A3NV5J9
Checked on ocp 4.11 cluster with payload 4.11.0-0.nightly-2022-04-11-200046. Step to check" 1. Install CodeReady Workspaces operator in cluster, then create a "CodeReady Workspaces instance Specification" instance. 2. Also create another consolelink crd 3. Check in Application Menu, now OCM and Code Ready appear under "Red Hat Applications", user created consolelink crd is located in another section which is set by user. Seems this is what the pr11268 has done. @Robb, if this is all for this bug? if so, the bug could be verified.
Hi, @yanpzhan@redhat.com. After much discussion, it was decided the only change to fix this bug was to change the existing, hard-coded instance of `Red Hat applications` for `OpenShift Cluster Manager` to `Red Hat Applications` so `OpenShift Cluster Manager` and `CodeReady Workspaces` appear in the same `Red Hat Applications` grouping. The bug fix does not change to make the section names case insensitive as we deemed that would be a breaking behavioral change that could have unintended consequences for anyone adding ConsoleLinks to the Application Menu. So the answer to your question is yes, that's all there is to the bug and the bug should be verified based on your steps to check. :)
Thanks, Robb! Move the bug to Verified based on Comment 4 and Comment 5.
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