I'm using provisioning (LDMS8.8 SP4) to set up our clientmachines and policy-tasks to update every client's software.
If I reinstall a machine (e.g. after a hdd failure), which already exists in LDMS, the provisioning task fails sometimes (on different/random distribution packages). It seems like the provisioning task interferes with an old policy-task which the client may already got assigned in the past (before the hdd crash). It looks like the old policytasks start to run while the provisioningtask is still active. Everything works fine if you delete the machine and re-add it via "Configuration / Bare Metal Server" - like a new machine (which in fact deletes all those old policytasks). But this is kinda annoying, because only LD-Admins can delete machines from the inventory.
Is there some workaround available to stop the provisioning task from starting other policy tasks until every provisioning job is done?
Thanks & best regards,