Support case 03823052 reported that a customer had a VM stuck in Provisioning status with only a VMINotExists Reason and the customer did not know how to resolve the problem. In this case it turned out the VM was requesting storage beyond what was available due to storage limits defined via ResourceQuota.

4.14.5

Consistently reproducible

1. Create a ResourceQuota in a namespace with requests.storage set to 40Gi (here's the one that was used in this case https://github.com/codeready-toolchain/host-operator/blob/7d449f8bdf5449a58b39bece32c8a00ab6192659/deploy/templates/nstemplatetiers/base1ns/ns_dev.yaml#L93-L103 )
2. Create a PVC that consumes 11Gi
3. Create a VM that requests storage of 30Gi

status:
  conditions:
    - lastProbeTime: '2024-05-19T03:42:00Z'
      lastTransitionTime: '2024-05-19T03:42:00Z'
      message: VMI does not exist
      reason: VMINotExists
      status: 'False'
      type: Ready
  printableStatus: Provisioning
  volumeSnapshotStatuses:
    - enabled: false
      name: rootdisk
      reason: PVC not found
    - enabled: false
      name: cloudinitdisk
      reason: 'Snapshot is not supported for this volumeSource type [cloudinitdisk]'

Status with reason indicating insufficient storage

https://redhat-internal.slack.com/archives/C017V3R4M08/p1716503648670999
https://redhat-internal.slack.com/archives/CHK0J6HT6/p1716365893313839