Could be good to report it as an issue with Gitlab - especially since it used to work fine in previous versions. Could just be a minor regression that needs to be fixed to add that support back in.
For us it was a “ü” and a “ö” in a label for open-id-connect. This maxed out 16 vCPUs and 32GB of RAM resulting in a non-availability of a Gitlab EE system at our university.
It’s been over 24 hours but the cpu is still 100%. I also did the security update. There is no change. The application is getting errors in the interface. For example; on board, when issues are opened
@CaptainsDT Please do not hijack people threads when they have nothing to do with the problem you are experiencing. This is the second time you did it now. I’ll request a Gitlab team member to separate your post out again into a separate topic. Only post in someones topic if it is exactly the same problem you are experiencing.
EDIT: seems you have a topic, so stick to it until people reply: gitlab-ce15.10.xRecovery failure rather than hijack other threads unrelated to your problem.