When we try to deleted the MachineOSConfig when it is still building state. Then the resources related to MOSC is deleted but not for configmap. And hence when we try to again apply the MOSC in same pool the status of MOSB is not properly generated. 

To resolve the issue we have to manually delete the resources created in configmap. 

$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.16.0-0.nightly-2024-07-10-022831   True        False         3h15m   Cluster version is 4.16.0-0.nightly-2024-07-10-022831

1. Create CustomMCP
2. Apply any MOSC
3. Delete the MOSC while it is still in building stage
4. Again apply the MOSC
5. Check the MOSB status
oc get machineosbuilds.
NAME                                                            PREPARED   BUILDING   SUCCEEDED   INTERRUPTED   FAILED
infra-rendered-infra-371dc5d02dbe0bb5712857393db95bf3-builder                                                   False

oc get machineosbuilds
 NAME                                                            PREPARED   BUILDING   SUCCEEDED   INTERRUPTED   FAILED infra-rendered-infra-371dc5d02dbe0bb5712857393db95bf3-builder                                                   False 

We should be able to see the status     

Check the logs of machine-os-builder
$ oc logs machine-os-builder-74d56b55cf-mp6mv | grep -i error I0710 11:05:56.750770       1 build_controller.go:474] Error syncing machineosbuild infra3: could not start build for MachineConfigPool infra: could not load rendered MachineConfig mc-rendered-infra-371dc5d02dbe0bb5712857393db95bf3 into configmap: configmaps "mc-rendered-infra-371dc5d02dbe0bb5712857393db95bf3" already exists