Kasten K10 7.5.2 DR failing - "Prior policy run ist still in progress"

Hello ​@virtualhobbit  There are likely ConfigMaps in the Kasten namespace that are blocking actions. Please run the following command and check if any ConfigMaps are present. If you find any, share their YAML files with me and delete the ones with the nslock suffix.

kubectl get cm -n kasten-io | grep nslock

Additionally, please restart all K10 deployments by performing a rollout restart and test again.

kubectl rollout restart deployment -n kasten-io


P.S. it would be greate if you list all the configmaps in kasten namespace and share it with me.

Thanks,
Ahmed Hagag

HI Ahmed,

Nothing comes back when grepping for nslock. These ConfigMaps are there:

aggauditpolicy-config
fluentbit-configmap
frontend-config
k10-config
k10-eula
k10-eula-info
k10-features
k10-gateway
kasten-prod-k10-metering-config
kube-root-ca.crt

I’ve restarted the deployments and now the DR policy runs successfully.

Thanks!

-Mark

Appears one DR ran and then since then we’ve been getting the same issue (see attached).

Anyone any ideas?

Was there possibly an update of Kasten which caused the issue? 

Hard to know now but as you restarted the deployment did it have a different age to all other deployments? I.e not changed after an update, possibly? 

Next thing from a support perspective would be to look at a support bundle, if this is a production environment then you can open a support case and we can investigate further.