Description

The issue is seen sporadically on clusters with 3 workers and kataconfig with node selector matching with single labeled node. This node appear eventually in the completedNodesList, but unInstallationStatus/inProgress stays True forever with
finalizers in metadata:
finalizers:
    - kataconfiguration.openshift.io/finalizer

Steps to reproduce

1. Deploy cluster with 3 workers
2. Label one of them and apply kataconfig with NodeSelector:
kataConfigPoolSelector:
      matchLabels:
        custom-kata1: test
3. Delete kataconfig

Expected result

kataconfig eventually disposed after runtime been removed from the node

Actual result

node is been rebooted and uninstalled, but kataconfig isn't disposed finally, creating an issue, can't apply another kataconfig, can't delete it permanently, only wipe out whole cluster

Impact

This can cause problems to test automation and in real deployment

Env

OCP 4.12.0-rc.6-x86_64

Additional helpful info

kataconfig will be attached