Verified on 4.10.0-0.nightly-2022-02-02-000921

$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2022-02-02-000921   True        False         3m50s   Cluster version is 4.10.0-0.nightly-2022-02-02-000921
$ oc -n openshift-machine-api get machinesets
NAME                                 DESIRED   CURRENT   READY   AVAILABLE   AGE
ci-ln-b7fit7k-72292-4wkqh-worker-a   1         1         1       1           23m
ci-ln-b7fit7k-72292-4wkqh-worker-b   1         1         1       1           23m
ci-ln-b7fit7k-72292-4wkqh-worker-c   1         1         1       1           23m
ci-ln-b7fit7k-72292-4wkqh-worker-f   0         0                             23m
$ oc -n openshift-machine-api get machinesets/ci-ln-b7fit7k-72292-4wkqh-worker-a -o yaml | grep image
            image: projects/rhcos-cloud/global/images/rhcos-410-84-202201251210-0-gcp-x86-64


matches snippet from boot image bump

       "gcp": {
          "release": "410.84.202201251210-0",
          "project": "rhcos-cloud",
          "name": "rhcos-410-84-202201251210-0-gcp-x86-64"
        }

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 (Moderate: OpenShift Container Platform 4.10.3 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:0056