[GCP] if disk is  boot:true image is getting reverted after creating machine in machineset spec

    4.19.0-0.nightly-2025-06-08-193046

    Always

1.Edit machineset use the image mentioned below in comments and update replicas as well to make sure new machine comes up in the cluster    
miyadav@miyadav-thinkpadx1carbongen8:~$ oc edit machineset jiwei-0609c-vc22n-worker-f --kubeconfig kk1 
machineset.machine.openshift.io/jiwei-0609c-vc22n-worker-f edited
miyadav@miyadav-thinkpadx1carbongen8:~$ oc edit machineset jiwei-0609c-vc22n-worker-f --kubeconfig kk1 
machineset.machine.openshift.io/jiwei-0609c-vc22n-worker-f edited
/*miyadav@miyadav-thinkpadx1carbongen8:~$ #projects/rhcos-cloud/global/images/rhcos-413-92-202402131523-0-gcp-x86-64 */


2.Check new machine came up and running 
miyadav@miyadav-thinkpadx1carbongen8:~$ oc get machine --kubeconfig kk1
NAME                               PHASE     TYPE            REGION        ZONE            AGE
jiwei-0609c-vc22n-master-0         Running   n2-standard-4   us-central1   us-central1-a   99m
jiwei-0609c-vc22n-master-1         Running   n2-standard-4   us-central1   us-central1-b   99m
jiwei-0609c-vc22n-master-2         Running   n2-standard-4   us-central1   us-central1-c   99m
jiwei-0609c-vc22n-worker-a-6jr79   Running   n2-standard-2   us-central1   us-central1-a   92m
jiwei-0609c-vc22n-worker-b-xnkjn   Running   n2-standard-2   us-central1   us-central1-b   92m
jiwei-0609c-vc22n-worker-c-vntns   Running   n2-standard-2   us-central1   us-central1-c   37m
jiwei-0609c-vc22n-worker-f-2wqng   Running   n2-standard-2   us-central1   us-central1-f   5m20s

3. the machine image we used earlier intact for machine but got reverted for machineset ( below details )
miyadav@miyadav-thinkpadx1carbongen8:~$ oc get machines jiwei-0609c-vc22n-worker-f-2wqng -o yaml --kubeconfig kk1 | grep -i image
        image: projects/rhcos-cloud/global/images/rhcos-413-92-202402131523-0-gcp-x86-64
miyadav@miyadav-thinkpadx1carbongen8:~$ oc get machineset jiwei-0609c-vc22n-worker-f -o yaml --kubeconfig kk1 | grep -i image
            image: projects/rhcos-cloud/global/images/rhcos-9-6-20250523-0-gcp-x86-64
     

machine comes up fine but the image in machineset gets reconciled

     Need to confirm if that is expected and agreed upon behavior to not use image for boot disk other than installed , then it should block changing it 

see that when specified type/osDisk.diskType/osImage in the install-config but the workers machineset seems ignoring the osImage settings, although the other 2 settings are applied  


 $ yq-3.3.0 r test2/install-config.yaml platform
gcp:
  projectID: openshift-qe
  region: us-central1
  defaultMachinePlatform:
    type: n2-standard-2
    osDisk:
      diskType: pd-balanced
    osImage:
      project: redhat-marketplace-dev
      name: redhat-coreos-opp-419-x86-64-20250513-02
$ 
$ oc get machinesets -n openshift-machine-api
NAME                         DESIRED   CURRENT   READY   AVAILABLE   AGE
jiwei-0609c-vc22n-worker-a   1         1         1       1           80m
jiwei-0609c-vc22n-worker-b   1         1         1       1           80m
jiwei-0609c-vc22n-worker-c   1         1         1       1           80m
jiwei-0609c-vc22n-worker-f   0         0                             80m
$ oc get machinesets -n openshift-machine-api jiwei-0609c-vc22n-worker-a -ojson | jq -r .spec.template.spec.providerSpec.value.disks
[
  {
    "autoDelete": true,
    "boot": true,
    "image": "projects/rhcos-cloud/global/images/rhcos-9-6-20250523-0-gcp-x86-64",
    "labels": {},
    "sizeGb": 128,
    "type": "pd-balanced"
  }
]
$ oc get machinesets -n openshift-machine-api jiwei-0609c-vc22n-worker-a -ojson | jq -r .spec.template.spec.providerSpec.value.machineType
n2-standard-2
$