Description

When undeploying peer pods, the podvm deletion job succeed but the podvm image still exist in azure.

Steps to reproduce

• Install OSC 1.8.0
• Deploy KataConfig for non-CoCo peer pods
• Wait for deployment to be complete
• Get the AZURE_IMAGE_ID from the peer pods CM

  $ oc get cm -n openshift-sandboxed-containers-operator peer-pods-cm -o yaml | grep AZURE_IMAGE_ID
    AZURE_IMAGE_ID: /subscriptions/<sensitive>/resourceGroups/aro-x9n3hg77/providers/Microsoft.Compute/galleries/PodVMGallery_d01b8b50/images/podvm-image/versions/0.0.2024111438
  

• Find the corresponding image :

  $ az image list -g aro-x9n3hg77 | grep /images/
      "id": "/subscriptions/<sensitive>/resourceGroups/aro-x9n3hg77/providers/Microsoft.Compute/images/podvm-image-0.0.2024111438",
  

• Delete KataConfig
• Wait for the podvm deletion job to complete
• Check if the podvm image still exists

Expected result

$ az image list -g aro-x9n3hg77 | grep 0.0.2024111438
$

Actual result

$ az image list -g aro-x9n3hg77 | grep 0.0.2024111438
    "id": "/subscriptions/<sensitive>/resourceGroups/aro-x9n3hg77/providers/Microsoft.Compute/images/podvm-image-0.0.2024111438",
$

Impact

Extra costs for the customer

Env

OCP 4.15.37 in ARO
OSC 1.8.0-7

Additional helpful info

User needs to `az login` with the same service principal that was used to create the podvm and `az delete` it manually.