1. Proposed title of this feature request   
   machine provisions with any image from projects/rhcos-cloud/global/images/ in openshift cluster deployed on GCP when image is not specified in the machineset

2. What is the nature and description of the request?

When machinesets created inside the openshift cluster having platform GCP, it takes any machine from projects/rhcos-cloud/global/images/

3. Why does the customer need this? (List the business requirements here)

The image is different for machine at the place of ideal image which should be 

It can lead to ignition version which will pause the provisioning of the image

The image section should be made compulsory because of this 

4. List any affected packages or components.

Machineset

Reproduced output:
We created one machineset without the Image reference in the template.spec.disk.image which lead to same situation where the machine booted with wrong image.

~~~
...
...
disks:

• autoDelete: true
  boot: true
  image: projects/rhcos-cloud/global/images/rhcos-414-92-202307070025-0-gcp-x86-64
  labels: {}
  sizeGb: 128
  type: pd-ssd

~~~

As per our understanding the image section is compulsory and should be provided else GCP will pick any available image from the link projects/rhcos-cloud/global/images/

Reference document that it is required field is below:

https://docs.redhat.com/en/documentation/openshift_container_platform/4.8/html/machine_management/creating-machine-sets#machineset-yaml-gcp_creating-machineset-gcp

~~~
Specify the path to the image that is used in current compute machine sets. If you have the OpenShift CLI installed, you can obtain the path to the image by running the following command:
$ oc -n openshift-machine-api \
-o jsonpath='

' \
get machineset/<infrastructure_id>-worker-a
~~~

Even after boot image management using the following documentation,

https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/machine_configuration/mco-update-boot-images#mco-update-boot-images_machine-configs-configure

If Image parameter is not passed in the machineset then it is taking the following image not the current version image

projects/rhcos-cloud/global/images/rhcos-414-92-202307070025-0-gcp-x86-64

But if image parameter is there in machineset manifest and we pass the wrong image in that, it reconciles it to the latest version,

Hence image parameter should be made mandatory for also enabling boot image management.