openstack: converter pods are sometimes not removed on archive

[bennyz]

I noticed some instances in which converter pods created by the convert job are not removed. The pods are currently removed manually[1] because I couldn't get the deletion to propagate to the pod, this does work when done manually with kubectl and should work when done with client-go

[1]

forklift/pkg/controller/plan/kubevirt.go

Line 336 in b83c914

// One day we'll figure out why client.PropagationPolicy(meta.DeletePropagationBackground) doesn't remove the pods

[ahadas]

what didn't add up is that I didn't notice this issue with the vddk-validation pod that is triggered the same way but I see that you say it's inconsistent so maybe that's what caused the failure to remove these pods when removing their job?...

[bennyz]

what didn't add up is that I didn't notice this issue with the vddk-validation pod that is triggered the same way but I see that you say it's inconsistent so maybe that's what caused the failure to remove these pods when removing their job?...

they're never removed when I only set the propagationpolicy vs. sometimes not removed when explicitly deleted