Red Hat Bugzilla – Bug 1509192
`oc debug` pod does not work and shows "cannot set blockOwnerDeletion if an ownerReference ..."
Last modified: 2017-11-28 17:21:23 EST
Description of problem: `oc debug` pod does not work and shows "cannot set blockOwnerDeletion if an ownerReference ..." Version-Release number of selected component (if applicable): First found in free-stg v3.7.0-0.178.2 (online version 3.6.0.35) Double reproduced in OCP v3.7.0-0.190.0 How reproducible: Always Steps to Reproduce: 1. Create any pod, e.g. create app via template "MySQL (Persistent)" 2. oc get pod NAME READY STATUS RESTARTS AGE dctest-1-4v89g 2/2 Running 0 11m mysql-1-85ldc 1/1 Running 0 9m 3. $ oc debug mysql-1-85ldc # pod dctest-1-4v89g is same Debugging with pod/mysql-1-85ldc-debug, original command: container-entrypoint run-mysqld Error from server (Forbidden): pods "mysql-1-85ldc-debug" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: User "xingxingxia" cannot update replicationcontrollers/finalizers in project "xxia-proj", <nil> 4. oc debug dc/mysql Debugging with pod/mysql-debug, original command: container-entrypoint run-mysqld Waiting for pod to start ... Actual results: 3. `oc debug` pod cannot work, but `oc debug` dc can Expected results: 3. oc debug pod should work Additional info:
Origin PR: https://github.com/openshift/origin/pull/17178
Verified in oc/OCP v3.7.0-0.196.0, thx Like for DC, `oc debug` pod works now: $ oc debug mysql-2-7vtp5 Debugging with pod/mysql-2-7vtp5-debug ... ... sh-4.2$
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188