The docs say there are three valid values for console's managementState but there are actually four. The undocumented state is "Force" - the docs should explain what the semantics are for this "Force" state.

See https://docs.openshift.com/container-platform/4.13/web_console/disabling-web-console.html#web-console-disable_disabling-web-console

4.13

Run "oc" and set managementState to "Foo" and see the error message mention a fourth state. Run "oc" and set managementState to "Force" and see it is successful. This "Force" state is an undocumented fourth state.

1. Run:

oc patch consoles.operator.openshift.io cluster -p '{"spec": {"managementState": "Foo" }}' --type=merge

and see the error message:

The Console "cluster" is invalid: spec.managementState: Invalid value: "Foo": spec.managementState in body should match '^(Managed|Unmanaged|Force|Removed)$'

Notice that forth state called "Force". That is not documented. Only the other three states are mentioned in the documentation. See: https://docs.openshift.com/container-platform/4.13/web_console/disabling-web-console.html where it says,

"Set the managementState parameter value to Removed to disable the web console. The other valid values for this parameter are Managed, which enables the console under the cluster's control, and Unmanaged, which means that you are taking control of web console management."

It has no mention of this fourth "Force" state. What is the semantics of this "Force" state?

2. Notice that "Force" is an actually supported state - just change to that state and see that it is successful. Run:

oc patch consoles.operator.openshift.io cluster -p '{"spec": {"managementState": "Force" }}' --type=merge

and it says "console.operator.openshift.io/cluster patched". Confirm the value is now Force by running:

oc get consoles.operator.openshift.io cluster -o jsonpath='{.spec.managementState}{"\n"}'

and it returns "Force"