whenever upgrading a minor version is posing a risk, such as with API removals, there is an admin gate mechanism that blocks minor upgrades, and displays blocking reason message (in "oc adm upgrade" output, as well as in cluster version operator conditions), up until the gate is acknowledged by admin.

however, whenever there's multiple admin gates in place, only first gate is displayed, leaving an admin oblivious for another gate existence, up until the first one is acknowledged. 

4.12.0-0.nightly-2023-03-10-133520 but observed elsewhere too

100%?

1. make sure there's multiple gates for the same version as the cluster

❯ oc -n openshift-config-managed get configmap admin-gates -o json | jq -r ".data"
{
  "ack-4.12-kube-1.26-api-removals-in-4.13": "Kubernetes 1.26 and therefore OpenShift 4.13 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/6958394 for details and instructions.",
  "ack-4.12-testing": "Acknowledge this to unblock updates to next minor version"
}

2. check "oc adm upgrade" output - only the first gate is displayed in "Message"

Cluster version is 4.12.0-0.nightly-2023-03-10-133520Upgradeable=False  Reason: AdminAckRequired
  Message: Acknowledge this to unblock updates to next minor version Kubernetes 1.26 and therefore OpenShift 4.13 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/6958394 for details and instructions.

 3.check cvo "Upgradeable" condition - again only the first gate

2023-03-12T15:27:31Z Upgradeable=False AdminAckRequired: Acknowledge this to unblock updates to next minor version Kubernetes 1.26 and therefore OpenShift 4.13 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/6958394 for details and instructions.

first out of multiple gates is displayed

all gates for the current version is displayed under both oc adm upgrade as well as in cluster conditions.