Regular user cannot open the debug container from pods they created

Solution In Progress - Updated -

Environment

  • Red Hat OpenShift Container Platform(RHOCP)
    • OCP 4.10
    • OCP 4.11

Issue

  • Regular user account cannot open debug container via UI, see the below error:

    pod "xxx" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: , <nil>

Resolution

The issue is currently under investigation in the Bug OCPBUGS-1522

Customer should still be able to troubleshoot their pods via the CLI.
See our OCP doc for further information

Root Cause

Normal user cannot open the "debug container" from the pods (crashLoopbackoff) they created - Bug OCPBUGS-1522

Diagnostic Steps

Verification Steps:

  1. Login OCP as a normal user
  2. Create a project and create a Pods with CrashLoopBackOff state
  3. Verify if the Debug container could be open without error message via the link
    • on Pod details -> Logs Tab
    • or Topology -> Resources Tab -> Pods section -> CrashLoopBackOff bubble window
  4. The error message should appear in Web UI:
pods "xxx" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: , <nil>

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments