chaos-operator icon indicating copy to clipboard operation
chaos-operator copied to clipboard

Running Litmus workflows in Openshift throws "cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on:"

Open sputmayer opened this issue 2 years ago • 0 comments

Bug

What happened: I deployed Litmus 2.6 on Openshift in a disconnected environment. While I had issues with RBAC for starting Litmus, I finally got everything working and Litmus seems to be running fine. Next I wanted to run the workflow to do some chaos experiments in the cluster

What you expected to happen: I expected the workflow to run or atlesat kickoff

How to reproduce it (as minimally and precisely as possible): Deploy it in an Openshift cluster

Anything else we need to know?:

When I try to schedule a workflow using Litmus Portal Chaos Hub I can see the following errors in the Workflow Operator.

pods "custom-chaos-workflow-1647427227-1647432738-3411883899" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: , " namespace=litmus workflow=custom-chaos-workflow-1647427227-1647432738 Also attaching the logs

LitmusWorkflowLogs.txt

sputmayer avatar Mar 17 '22 01:03 sputmayer